From: "Richard B. Johnson" <root@chaos.analogic.com>
To: Valdis.Kletnieks@vt.edu
Cc: Boszormenyi Zoltan <zboszor@freemail.hu>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] Autoregulate vm swappiness cleanup
Date: Tue, 28 Oct 2003 10:54:56 -0500 (EST) [thread overview]
Message-ID: <Pine.LNX.4.53.0310281048130.21561@chaos> (raw)
In-Reply-To: <200310281539.h9SFdixF024951@turing-police.cc.vt.edu>
On Tue, 28 Oct 2003 Valdis.Kletnieks@vt.edu wrote:
> On Tue, 28 Oct 2003 09:39:53 EST, "Richard B. Johnson" said:
> > On Tue, 28 Oct 2003, Boszormenyi Zoltan wrote:
> > [SNIPPED...]
> >
> > > -rw-rw-r-- 1 zozo zozo 1090912 okt 27 22:54 interface.c
> > ^^^^^^^
> > Guess you use `vim` to edit ...eh?
> >
> > Linux does have a good linker, you know. You don't need to put
> > everything in one file!
>
> On the flip side, if there's a lot of routines all declared 'static' so they are
> only visible to that .c file, it's less than simple to split them out and
> tell the *rest* of the projects that 'routines in interface/*.c are visible
> to each other, but not to C code in database/*.c'.
>
> The Linux kernel has the same issues:
>
> % find . -name '*.[ch]' | xargs grep acpi_bus_unregister_driver
>
> referenced only in drivers/acpi and one include file - but pollutes the global
> linkage namespace all the same.
>
I keep hearing 'pollutes the global namespace' all the time, now. Do
you mean that 'C' code designers actually intend to use the same
name for different procedures or objects in different files?
If so, that's a problem of idiocy, not pollution. Anybody who
writes code for a living would not do that, now would they??
The fact that there may be many global references that need to
be resolved by the linker is not pollution. It's using tools to
simplify design, implementation, testing, and maintenance.
Cheers,
Dick Johnson
Penguin : Linux version 2.4.22 on an i686 machine (797.90 BogoMips).
Note 96.31% of all statistics are fiction.
next prev parent reply other threads:[~2003-10-28 15:53 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-28 13:34 Boszormenyi Zoltan
2003-10-28 14:39 ` Richard B. Johnson
2003-10-28 15:39 ` Valdis.Kletnieks
2003-10-28 15:54 ` Richard B. Johnson [this message]
2003-10-28 16:37 ` Valdis.Kletnieks
2003-10-28 16:51 ` Måns Rullgård
2003-10-28 17:33 ` Valdis.Kletnieks
2003-11-03 8:15 ` [OT] " Boszormenyi Zoltan
-- strict thread matches above, loose matches on Subject: below --
2003-10-23 13:37 [PATCH] Autoregulate vm swappiness 2.6.0-test8 Con Kolivas
2003-10-23 14:42 ` Martin J. Bligh
2003-10-23 15:03 ` Con Kolivas
2003-10-25 6:58 ` [PATCH] Autoregulate vm swappiness cleanup Con Kolivas
2003-10-26 11:22 ` Nick Piggin
2003-10-26 10:36 ` Con Kolivas
2003-10-26 11:42 ` Nick Piggin
2003-10-28 11:04 ` Pavel Machek
2003-10-28 12:40 ` Con Kolivas
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Pine.LNX.4.53.0310281048130.21561@chaos \
--to=root@chaos.analogic.com \
--cc=Valdis.Kletnieks@vt.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=zboszor@freemail.hu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®