RE: [PHP] comment followed by ?> fails to parse

I disagree. I use // because then when I need to take out a chunk of code (the requirements for the programs change faster than I can keep up with them!!) I can do /* unnecessary code */ and it doesn't end prematurely. -Natalie -----Original Message----- From: Ed Gorski [mailto:gorskie@spjc.edu] Sent: Wednesday, May 29, 2002 9:25 AM To: php-general@lists.php.net; php-general@lists.php.net Subject: Re: [PHP] comment followed by ?> fails to parse Bah quit complaining, you should be using /* comments */ anyway..... ed At 09:16 PM 5/29/2002 +0800, Jason Wong wrote: >On Wednesday 29 May 2002 21:10, Brinkman, Theodore wrote: > > It really should ignore anything in any sort of comment. The whole > > point of a comment is that it provides the programmer with > > information and is ignored by the compiler/interpreter. If // is > > supposed to comment until the end of the line, then by god, it > > should comment until the end of the line, not until the end of the > > line unless it finds ?> buried in the line somewhere. Even VB gets > > this right! > >As someone has already pointed out that is documented behaviour. >Personally I agree with you in that the whole line should be commented. > >-- >Jason Wong -> Gremlins Associates -> www.gremlins.com.hk >Open Source Software Systems Integrators >* Web Design & Hosting * Internet & Intranet Applications Development * > >/* >"Life is too important to take seriously." > -- Corky Siegel >*/ > > >-- >PHP General Mailing List (http://www.php.net/) >To unsubscribe, visit: http://www.php.net/unsub.php -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php