Re: \n after ?> CS Stupid?

+100 here, it's impossible to visually check for 1 or many \n's in most editors (or code browsers). - hence removing the ?> requirement is far more sensible.. Regards Alan On Sun, 2005-09-18 at 13:42 -0400, Davey Shafik wrote: > Hey, > > Sorry for the somewhat cryptic subject, I am referring to the > last point on this page: > > http://pear.php.net/manual/en/standards.file.php > > If we mandate that all files should have a single \n after the closing > ?> we run the risk of people including PEAR stuff before doing headers > stuff and running into Headers already sent errors. I don't know who on > earth though this was a good idea. Is there some reason for this that I > have no idea about? > > Please can we remove this? And in fact, mandate the opposite, no > code should output anything outside of <?php and ?> > > - Davey >