On Saturday 15 November 2003 08:22 pm, Chris Shiflett wrote:
> 1. When a closing PHP tag, such as ?>, is followed by a newline, the
> newline is not output.
Im the original author to this thread, and this is an attempt to bring back
this thread to square one, as it was straying in other directio
--- Keith Greene <[EMAIL PROTECTED]> wrote:
> It's not a bug. Anything (including spaces, newlines etc) that is not
> inside is output directly to the browser.
There are two different things being discussed, and I'm not positive which
is considered a bug.
1. When a closing PHP tag, such as ?>,
Keith Greene wrote:
Ok, you're getting into semantics now.
http://www.php.net/manual/en/language.basic-syntax.php doesn't say
whether it is acceptable or not, but as Robert pointed out, if your
script is purely php, omitting it is a good way of eliminating the
headache of trailing white spaces
Ok, you're getting into semantics now.
http://www.php.net/manual/en/language.basic-syntax.php doesn't say whether
it is acceptable or not, but as Robert pointed out, if your script is
purely php, omitting it is a good way of eliminating the headache of
trailing white spaces that may interfere w
Keith Greene wrote:
That's not a bug either. Leaving out the ?> is simply telling the php
parser that it has to parse the rest of the script.
Where's the manual page saying that's allowed?
--
The above message is encrypted with double rot13 encoding. Any unauthorized attempt
to decrypt it will
Keith Greene wrote:
It's not a bug. Anything (including spaces, newlines etc) that is not
inside is output directly to the browser.
No, I'm talking about not using ?>.
--
The above message is encrypted with double rot13 encoding. Any unauthorized attempt
to decrypt it will be prosecuted to th
Yep. It allows you to only use php where needed, and use HTML for the rest.
At 04:02 PM 11/15/2003, you wrote:
On Sat, 2003-11-15 at 18:49, Leif K-Brooks wrote:
> Robert Cummings wrote:
>
> >FYI, if you're woprried about the "header cannot be sent due to
> >output..." error, then if your file only
On Sat, 2003-11-15 at 18:49, Leif K-Brooks wrote:
> Robert Cummings wrote:
>
> >FYI, if you're woprried about the "header cannot be sent due to
> >output..." error, then if your file only has code and no HTML, then you
> >can omit the ?> tag at the end of your script. This solves countless
> >issu
It's not a bug. Anything (including spaces, newlines etc) that is not
inside is output directly to the browser.
At 03:49 PM 11/15/2003, you wrote:
Robert Cummings wrote:
FYI, if you're woprried about the "header cannot be sent due to
output..." error, then if your file only has code and no HTML
Robert Cummings wrote:
FYI, if you're woprried about the "header cannot be sent due to
output..." error, then if your file only has code and no HTML, then you
can omit the ?> tag at the end of your script. This solves countless
issues with there being a space, a tab, a newline, or any whitespace
a
On Sat, 2003-11-15 at 12:12, Chris Shiflett wrote:
> --- Gerard Samuel <[EMAIL PROTECTED]> wrote:
> > Most of the time, I edit files via the command line, (FBSD). When
> > the files are saved, it adds a \n (newline) character (at least I
> > believe that is what it is) after the closing ?> When vie
--- Gerard Samuel <[EMAIL PROTECTED]> wrote:
> Most of the time, I edit files via the command line, (FBSD). When
> the files are saved, it adds a \n (newline) character (at least I
> believe that is what it is) after the closing ?> When viewing these
> files in a windows GUI editor, there is an ext
Most of the time, I edit files via the command line, (FBSD).
When the files are saved, it adds a \n (newline) character (at least I believe
that is what it is) after the closing ?>
When viewing these files in a windows GUI editor, there is an extra line
after the ?> closing tag.
Using the php func
13 matches
Mail list logo
