Re: Re: headers and newline at end of script
| From: | Robert Cummings | Date: | Thu, 20 Jul 2006 21:06:10 +0000 |
| Subject: | Re: Re: headers and newline at end of script | ||
| References: | 1 2 3 4 | Groups: | php.general |
| Request: | Send a blank email to php-general+get-239665@lists.php.net to get a copy of this message | ||
On Thu, 2006-07-20 at 16:50, Jochem Maas wrote:
> Robert Cummings wrote:
> > On Thu, 2006-07-20 at 14:15, Martin Marques wrote:
> >> On Thu, 20 Jul 2006 13:06:10 -0400, Robert Cummings <robert@interjinn.com>
> >> wrote:
> >>> On Thu, 2006-07-20 at 12:12, Adam Zey wrote:
> >>>> Martin Marques wrote:
> >>>> > Now, my question is: Is it a bad practice to "NOT" close the
> >>>> > script
> >>>> with
> >>>>> the PHP closing "?>"? I mean, just leave the script without a
> >>>>> closing
> >>>>> PHP simbols, as this scripts are included?
> >>>> Yes.
> >>> Wrong :)
> >> Why? ;-)
> >
> > See links I posted in previous response >:)
>
> I don't understand - the links point to posts by Rasmus saying that's
> 'beneficial' - seems to me to be a fairly robust endorsement yet you
> consider leaving off trailing '?>' wrong (and use Rasmus' comments to
> back that up)
>
> we're having another heatwave here in europe so that
> could be compounding my lack of understanding ;-)
The original question says "Is it bad practice?" Adam Zey said "Yes". I
said he is "Wrong". Now granted, re-reading the original post, there are
two questions, I presumed (quite possibly incorrectly) Adam Zey was
answering the first. Generally when you have Y answers for X questions
and Y < X then the first Y questions are presumed answered. Just like
when parsing CSV files and you run out of commas :) If we didn't have
this basic presumption, then the universe would begin to tear apart --
trust me on that one ;)
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. |
`------------------------------------------------------------'