Re: \n after ?> CS Stupid?
| From: | Daniel Convissor | Date: | Sun, 18 Sep 2005 17:52:58 +0000 |
| Subject: | Re: \n after ?> CS Stupid? | ||
| References: | 1 2 | Groups: | php.pear.qa |
| Request: | Send a blank email to pear-qa+get-3035@lists.php.net to get a copy of this message | ||
Hi:
On Sun, Sep 18, 2005 at 07:48:18PM +0200, Arnaud Limbourg wrote:
>
> I agree it should be removed, I usually don't have one and even remove
> it when I see one. I have no idea why it is there.
It's been discussed a few times. This is for two reasons.
Unix files are supposed to have an \n after the last character (or
whatever you want to call it).
If they're not there, some editors add them automatically. So, having
them there all the time reduces the silly "No newline at end of file"
messages found frequently in CVS commits.
The real discussion should be why don't we rip out the "?>" in the first
place. :)
--Dan
--
T H E A N A L Y S I S A N D S O L U T I O N S C O M P A N Y
data intensive web and database programming
http://www.AnalysisAndSolutions.com/
4015 7th Ave #4, Brooklyn NY 11232 v: 718-854-0335 f: 718-854-0409