>>> And there remains issue with "nested" comments.
>>>       
> MD> No issue; no nesting.  Ergo, I'm not changing it.  In reply, rather than
> MD> quoting boring old pre-ISO C compiler options, please instead trace 
> support
> MD> back to the far more enriching Magna Carta.  King John of England's
>
>      "Enriching Magna Carta"? Sorry, Michael, you as always very vivid and,
> thus, very hard to understand (by English non-native).  :(
>   

I don't have my copy of Kernighan & Ritchie's "C Programming Language 
(ed. 2)" with me to show you, but here is an excerpt from ISO/IEC 
9899:TC2 WG14/N1124 Committee Draft - May 6, 2005 (6.4.9 Comments, page 
66) that says the same thing:

> Except within a character constant, a string literal, or a comment, 
> the characters /*
> introduce a comment. The contents of such a comment are examined only 
> to identify
> multibyte characters and to find the characters */ that terminate it.

With a footnote that says simply: "Thus, /* ... */ comments do not nest."


Some pre-ISO C compilers would barf if you had commented-out a statement 
like so:

/* i++; /* increment the index */

..because the compiler would see "/*" after "/*" and think that it 
should try to nest the comments. But in fact, according to ISO, comments 
CANNOT be nested and it doesn't matter what else you have after "/*" up 
until the next "*/". That's how I've always known C comments to work, 
after ISO.

Although I hear King John of England only programmed in LISP, so nested 
C comments weren't a problem for him. :-)

-jh


-- 
I'm sorry my president's an idiot. I didn't vote for him.


-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Freedos-devel mailing list
Freedos-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-devel

Reply via email to