From: "Robert Comer" 

> It is different from #ifdef (or #ifndef if you wish ;-) in that #ifdef is
> not a comment - comments are comments, #ifdef is a compiler directive of
> which only purpose is to state something to the compiler.

Or the interpreter.   (I really don't see much difference.....)

>Leaving comments
> out should not alter the behaviour of what is
executed/interpreted/compiled,
> while leaving out #ifdef's most certainly can and even should.

It wouldn't alter the behavior in a browser that didn't understand those
directives in the first place.

- Bob Comer


"Antti Kurenniemi"  wrote in message
news:3f8ead5a$1{at}w3.nls.net...
> "Robert Comer"  wrote in message
> news:3f8ea0fa{at}w3.nls.net...
> > > It's not sneaky, it's lame & it's a loathsome way of shoving in
> > > processing instructions. Comments should mean that. i.e. for humans.
> > > Using them to form part of / create the documentation for a human to
> > > read (e.g. javadoc) OK but putting processing instructions in there is
> > > simple lazy bodging.
> >
> > I don't agree -- it's a good way to program an interpreted language for
> > different abilities, yet keep the very same code running on different
> > platforms. It's really no different than a #ifndef...
>
> It is different from #ifdef (or #ifndef if you wish ;-) in that #ifdef is
> not a comment - comments are comments, #ifdef is a compiler directive of
> which only purpose is to state something to the compiler. Leaving comments
> out should not alter the behaviour of what is
executed/interpreted/compiled,
> while leaving out #ifdef's most certainly can and even should.
>
>
> Antti Kurenniemi
>
>

--- BBBS/NT v4.01 Flag-5