Eric Butera wrote:
On Sat, Jan 31, 2009 at 10:10 AM, tedd <tedd.sperling@xxxxxxxxx> wrote:
My mother always told me to close the door. She wasn't a programmer, but it
kept the chickens out.
As a matter of habit, I always close all tags. However, I have yet to be
bitten by the problem everyone speaks about (knock on wood).
Cheers,
tedd
--
-------
http://sperling.com http://ancientstones.com http://earthstones.com
--
PHP General Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php
Right, but the problem isn't us, its them. I don't have this problem
myself (since I figured out why I was getting those lame headers sent
errors years ago), but when we work in teams... well.. all bets are
off. :(
personally I close and ensure no trailing space; however I have been
trying to remove the ?> recently for files with nothing but php - purely
to save others grief who may use the code, as I did come across this
error again recently.
specifically the error in my scenario was called by a DOS format php
file with trailing lines on a linux box - so I'm guessing that /n is
trimmed but that leaves the /r which is output on linux systems; hence
the error.
although, in a world of tags and markup there's something that really
grates about opening with <?php and not closing it.!
--
PHP General Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php
