|
|
Posted by d43m0n AT shaw DOT ca on 10/11/37 11:55
Luka M. wrote:
> "JimL" <me@privacy.net> wrote in message
> news:mooed21seg1mi3lf4h5j0ocnrsh3vdgqhd@4ax.com...
> > On 6 Aug 2006 00:19:18 -0700, "d43m0n AT shaw DOT ca" <d43m0n@shaw.ca>
> > wrote:
> >
> > >
> > >J.O. Aho wrote:
> > >> Luka M. wrote:
> > >> > snip
> >
> > >> What about showing the source you are using, it's easier to see if you
> do
> > >> something wrong there that way, otherwise recompile php.
> > >>
> > >>
> > >> //Aho
> > >
> > >It's sad, they always blame it on someone else... do us all a favour,
> > >RTFM. And then come back with a question...
> >
> > Yes, it is sad. But it a common thead that runs thruout human
> > history. Must be human genetics.
> >
> > Therefore, it is not going away so we should accept that it will
> > repeat itself and come up with a plan to manage it as efficiently as
> > possible.
> >
> > 1. Get them to clarify their stance.
> > 2. Show them the ignorance of their claim.
> > 3. Hold them accountable for their stance.
> > 4. .....
>
> Sorry, no source, but it works like this:
> Gets a file content to a string (just print it to screen, you'll se it's
> different, and count chars, shows more), replaces \n's (different methods
> tested), but some kind of space that's not really a space (try to replace it
> as " " - doesent work) allways come up after the place where the replaced \n
> was.
> Maby that's the way it's supposed to be (probbably), but I see no logic in
> it.
> Tanks.
This sounds like your array returns an additional space between your
lines during print_r() returns..
What if you used trim() for each of your array items?
Navigation:
[Reply to this message]
|