Re: [9fans] plan9's C compiler and // comments

["boyd, rounin" <boyd@insultant.net>]

> I did the special /**/ stuff because some crappy code depends on
> them being elided.  I probably should have done // as well but
> decided not to for some reason lost in the past.

i wrote a cpp once, when i really wasn't up to the job.

the problem is:

    do you remove the comment from the macro text or just
    leave it in?

in the case of /* ... */ it doesn't make a lotta difference 'cos
during the expansion they could dissappear.

if the case of // they had better be removed from the macro
text 'cos when the expansion comes along you are in a
'world of pain'.

reiser's cpp was blinding fast, and almost unreadable so
you had your work cut out to work out the semantics of
the damn thing.

he had worked out this insight that you were just writing
a _slightly_ smarter version of cat;  it didn't tokenise
much and used one i/o buffer to do all the dirty work.