Re: More Standards - no ?> at end of file
| From: | Roman Neuhauser | Date: | Thu, 04 Dec 2003 17:28:03 +0000 |
| Subject: | Re: More Standards - no ?> at end of file | ||
| References: | 1 2 3 4 | Groups: | php.pear.dev |
| Request: | Send a blank email to pear-dev+get-24145@lists.php.net to get a copy of this message | ||
# davey@php.net / 2003-12-04 17:05:38 +0000:
> Roman Neuhauser wrote:
> ># davey@php.net / 2003-12-04 01:10:36 +0000:
> >>Alan Knowles wrote:
> >>>In the vain of 'you can never have enough standards'
> >>>
> >>>How about adding the condition that PEAR files should not be closed with
> >>>?>
> >>>
> >>>This has a couple of benefits.
> >>>- prevents output accidentally occuring and breaking sessions/cookies
> >>>etc..
> >>>- one less token to parse..
> >>>
> >>>Thoughts.......
> >>>
> >>>Regards
> >>>Alan
> >>
> >>Big -1 on this. What a bad idea.
> >
> > Yes, Davey. What exactly about the proposal is a bad idea?
>
> Its a cop out. Anyone with a PEAR account should be intelligent enough
> to not need to do this. If they're not, perhaps we should re-consider
> their membership status. Whilst I do believe there MIGHT be a reason to
> leave the '?>' off, I think thats something that should be brought to
> the attention on the list and if thats the case we'll say "OK, thats fine".
There's quite a lot of people with PEAR accounts who can't handle
cvs, "pear install ./package.xml", writing meaningful commit
messages, obeying format of files they edit (lf vs. crlf), and so
on. Why should this particular issue be anything special?
Hm, could people who use HomeSite for PEAR development raise your
hands please? How do you save a file in it that:
* doesn't end with "?>\r\n\r\n"
* is not binary
--
If you cc me or remove the list(s) completely I'll most likely ignore
your message. see http://www.eyrie.org./~eagle/faqs/questions.html