On Sat, 2003-11-15 at 12:12, Chris Shiflett wrote: > --- Gerard Samuel <[EMAIL PROTECTED]> wrote: > > Most of the time, I edit files via the command line, (FBSD). When > > the files are saved, it adds a \n (newline) character (at least I > > believe that is what it is) after the closing ?> When viewing these > > files in a windows GUI editor, there is an extra line after the ?> > > closing tag. Using the php function headers_sent(), doesn't show that > > there is any output being created by these extra lines after closing > > ?> > > > > So is "white space" only physical space (\s) or can it be anything > > like \t \r \n??? > > This is a feature/bug of PHP, depending on your perspective. When a > closing ?> is followed by a newline, the newline is not output.
FYI, if you're woprried about the "header cannot be sent due to output..." error, then if your file only has code and no HTML, then you can omit the ?> tag at the end of your script. This solves countless issues with there being a space, a tab, a newline, or any whitespace after the closing tag. Cheers, Rob. -- .------------------------------------------------------------. | InterJinn Application Framework - http://www.interjinn.com | :------------------------------------------------------------: | An application and templating framework for PHP. Boasting | | a powerful, scalable system for accessing system services | | such as forms, properties, sessions, and caches. InterJinn | | also provides an extremely flexible architecture for | | creating re-usable components quickly and easily. | `------------------------------------------------------------' -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
