Re: 4.0.5 Comments change (leads to inappropriate parse error based on contents of comments)

hi there, actually, the behavior you experienced with previous versions was buggy. current behavior is correct (and matches documentation, which has claimed this behavior for long). At 02:54 5.4. 2001, Steven Roussey wrote the following: -------------------------------------------------------------- >Hi, > >I found our problem. In 4.0.5, comments seem to be parsed differently. We >have ASP style tags enabled so we can use %> as well as ?>. But we had >comments like this: > ><? > >//asdfasdf%>asdfasdf >echo(''); >?> > >< 4.0.5 would ignore the whole line. 4.0.5 still parses it for open and >close tags. The lines above get handled differently from 4.0.4 to 4.0.5. It >is hard to track if the comment is inside a class, because there is no parse >error until the end of the file, and the code is not spit out like HTML (as >in the example above) because it is compiling the file. I think this is a >bug. We can clean up our code to fix it (and will), but.... > >Sincerely, > >Steven Roussey >Network54.com >http://network54.com/?pp=e > > >-- >PHP Development Mailing List <http://www.php.net/> >To unsubscribe, e-mail: php-dev-unsubscribe@lists.php.net >For additional commands, e-mail: php-dev-help@lists.php.net >To contact the list administrators, e-mail: php-list-admin@lists.php.net ------end of quote------ cynic@mail.cz ------------- And the eyes of them both were opened and they saw that their files were world readable and writable, so they chmoded 600 their files. - Book of Installation chapt 3 sec 7