"Richard Krehbiel" <rich@kastle.com> wrote in message news:alnr7q$1iu$1@digitaldaemon.com...
> "Walter" <walter@digitalmars.com> wrote in message news:all4cc$2qfk$1@digitaldaemon.com...
> >
> > "Richard Krehbiel" <rich@kastle.com> wrote in message news:alkre0$2fim$1@digitaldaemon.com...
> > > Why not just run a CPP tool on the D source before compiling it with
D?
> > > That'll take care of the #defined symbols (and, incidentally, the
> > #includes)
> > > for you.
> >
> > That is certainly possible, but I personally want to leave the
> preprocessor
> > behind and not perpetuate it.
>
> I've a ton of build scripts/makefiles with yacc, lex, awk, m4, esql, sqlj, and various custom source pre-processing steps.  If you're dead set
against
> a cpp phase, then I'd also like you to consider all those as well.
>
> Hmmm.  That's what I thought.

If you do want to preprocess D source, wouldn't one of those make a much better preprocessor than the C one? I am not so much against running D source through a preprocessor as I am opposed to making a particular preprocessor a defined part of the D language.