News for hackers. Stuff that matters.
Re:The Good, the Bad, and the Ugly: The Unix Legacy (by Rob ... by ars on Wednesday May 06, 2009 @08:29PM (#597120)

  And it has some horrible mistakes: (Ugly)
    The preprocessor
    Conditional compilation
Quite disagree - this feature is what makes C programs so portable.

And yes I saw the thing about Plan 9 compiling a kernel for all arch's with no ifdefs - well they only way you can do that is by cheating and either making your own preprocessor, or a fancy makefile. So big whoop.

I read some more, but rapidly came to the conclusion that this is unreadable without the associated (verbal) commentary.

Re:The Good, the Bad, and the Ugly: The Unix Legacy (by Rob ... by silentbicycle on Wednesday May 06, 2009 @08:50PM (#597161)
Elsewhere in the plan9 writings, Rob Pike says that he structured it by putting all of the stuff that would need to be ported in one group of files (which export the same interface), conditionally compiling the relevant subset of those, and then writing everything else in terms of those. (A better packaging/namespace system could handle this much more elegantly, though.)

Also, the C preprocessor is largely ignorant of C syntax. Am I the only one who finds that incredibly strange?

Re:The Good, the Bad, and the Ugly: The Unix Legacy (by Rob ... by philwelch on Thursday May 07, 2009 @03:16AM (#597588)
If the preprocessor knew the syntax, it would happen after parsing rather than before, which is exactly how every language other than C handles things that C handles using the preprocessor (turning "using" or "include" or "import" into keywords instead of preprocessor directives). I'm really not sure in what way it would be a pre-processor at that point.

So perhaps it's more accurate to say preprocessors aren't particularly useful.

Re:The Good, the Bad, and the Ugly: The Unix Legacy (by Rob ... by vorador on Thursday May 07, 2009 @12:29AM (#597415)
What would be the advantages of a preprocessor knowing the syntax ?
Re:The Good, the Bad, and the Ugly: The Unix Legacy (by Rob ... by silentbicycle on Thursday May 07, 2009 @09:35AM (#597885)
While it probably wouldn't be as useful as Lisp macros, due to the comparatively complex syntax, it would at least avoid bugs involving things like #define macros that evaluate their arguments multiple times.

OTOH, not having the C pp tied to C means it can be used for other stuff. The only thing I can think of offhand that uses it is the BSD calendar system, though, and that's largely just #include.

Re:The Good, the Bad, and the Ugly: The Unix Legacy (by Rob ... by devin on Thursday May 07, 2009 @04:07AM (#597632)
"And yes I saw the thing about Plan 9 compiling a kernel for all arch's with no ifdefs - well they only way you can do that is by cheating and either making your own preprocessor, or a fancy makefile. So big whoop."

I think that's a rather reductionist assessment. See: http://ntu.csie.org/~piaip/plan9/archives/000005.html

Re:The Good, the Bad, and the Ugly: The Unix Legacy (by Rob ... by ars on Thursday May 07, 2009 @04:19AM (#597636)
"Conditional compilation, even with #ifdef, is used sparingly in Plan 9. The only architecture-dependent #ifdefs in the system are in low-level routines in the graphics library."

So, in other words - yah, you need need a preprocessor with ifdef's, because sometimes there is no other way to do it.

And in other places he basically says he avoided ifdef's by using a fancy makefile, which doesn't seem an improvement to me, since the makefile essentially becomes a (less flexible) pre-processor.

The point about dead-branch pruning instead of ifdef is well taken though. (But there are cases where that doesn't work.)

Re:The Good, the Bad, and the Ugly: The Unix Legacy (by Rob ... by beza1e1 on Thursday May 07, 2009 @03:12AM (#597584)
His point is to use C instead of the preprocessor.

    #ifdef MIPS
        mips_stuff();
    #endif
should be

    if (MIPS) {
        mips_stuff();
    }
Even a mediocre compiler should be able to eliminate the then-body in the non-MIPS case.

Another possibility is to generate the same symbols in every architecture specific component and link the one you want to use.