Comments for PHP and newline characters

Comment from waffle.wootest.net on 2007-05-11

2007-05-11T16:15:57Z

This might be because some UNIX tools add a newline to files, and some PHP includes handling header-level output are written like that. If their inclusion would print the newline, the output would be started and headers prevented from being sent.]]>

Comment from Brad Choate on 2007-05-11

2007-05-11T22:08:45Z

@waffle.wootest.net: An interesting edge-case, but one that could be handled by only applying this rule to end-of-file situations. And even then, an ini setting to preserve whitespace should still trump that. For some, every byte is precious. Even the invisible ones.]]>

Comment from waffle.wootest.net on 2007-05-11

2007-05-11T22:22:24Z

Sure - although that would take the consistency out of it. It was only a theory, if one I deemed plausible.

An ini setting would be disastrous. Apply that to the file I described with trailing newline and headers being set, and consider some poor chap trying it on his home server (untweaked ini) and his host (diddled-with ini). Even if it didn't have those effects, I think it'd be a picky thing to have a setting for. PHP doesn't need more settings at this stage. ;)

]]>

Comment from Don on 2007-05-12

2007-05-12T19:03:57Z

"...so this may be well accepted in the PHP community."

I assume you mean "may not be well accepted."

]]>

Comment from Brad Choate on 2007-05-12

2007-05-12T19:08:13Z

@Don: No, I meant may be well accepted. I wasn't referring to my post, but to the behavior I am describing. I figure those that are more familiar with this peculiarity have come to terms with it, but I haven't.]]>

Comment from JazzMan on 2007-05-18

2007-05-18T12:46:28Z

I don't think this is a PHP problem. The behaviour you describe is happening outside the PHP block. As such, it is outside the control of PHP. It seems to be a symptom of how HTML is interpreted and thus is server and/or browser dependent.]]>

Comment from Brad Choate on 2007-05-18

2007-05-18T13:38:50Z

@JazzMan: Nope, this is definitely a PHP issue. It's even documented in their FAQ. You can observe this happening using the PHP command-line tool as well, so it's not something the browser is doing either.]]>