Thanks for the response - I found the answer to Q1 - the problem of
formatting newlines - I was running the code outputting to browser - and
got lazy on some - just pasting the PHP manual examples code directly,
without bracketing with HTML tags such as pre ... etc. Of course that
won't
Peter Lind wrote:
On 23 September 2010 21:47, YAD(YetAnotherDavid) ani...@mail.com wrote:
This code is 95% cut and paste from the PHP manual examples -
the Types/Strings/Heredocs section and the Filesystem/fnmatch pages.
There are actually two questions here - I have combined the code into one
On 24 September 2010 12:49, YAD(YetAnotherDavid) ani...@mail.com wrote:
Peter Lind wrote:
On 23 September 2010 21:47, YAD(YetAnotherDavid) ani...@mail.com wrote:
This code is 95% cut and paste from the PHP manual examples -
the Types/Strings/Heredocs section and the Filesystem/fnmatch pages.
This code is 95% cut and paste from the PHP manual examples -
the Types/Strings/Heredocs section and the Filesystem/fnmatch pages.
There are actually two questions here - I have combined the code into
one test file ... the strings in the code contain the questions ..
at the end I have inserted
On 23 September 2010 21:47, YAD(YetAnotherDavid) ani...@mail.com wrote:
This code is 95% cut and paste from the PHP manual examples -
the Types/Strings/Heredocs section and the Filesystem/fnmatch pages.
There are actually two questions here - I have combined the code into one
test file ... the
As far as I know, you wont get any line breaks.
I would suggest putting the results into pre/pre tags to preserve
formatting.
whenever I do a print_r(), i also encapsulate it within a pre/pre
tag so it is readable.
on another note, when I use variables within double quotes (or even
the heredoc
6 matches
Mail list logo
