maybe php.general would be more appropriate
im not a developer, but i think this "feature" doesnt make sense hehe
i think ob display handlers are not supposed to output things directly,
they just return them to the function that will output it
at your first snip, you could/should do:
at the seco
The 2 first bugs where really bogus, but imho the last one did make sense.
If stripslashes does "Un-quote string quoted with addslashes()", how
addslashes would come up with:
> c:\windows\system32
from:
> c:windowssystem32
?
Maybe its to late for a change, now that most people are used to this
b
ne that
hasn't put enough thought on it would think hehe
To sum up: why was the real way choosen?
Rasmus Lerdorf wrote:
On Thu, 10 Jun 2004, Andre Cerqueira wrote:
The 2 first bugs where really bogus, but imho the last one did make sense.
If stripslashes does "Un-quote string quoted wit
e:
On Thu, 10 Jun 2004, Andre Cerqueira wrote:
> But the manual doesn't say that it *only* removes slashes
> added by addslashes.
"Returns a string with backslashes stripped off. (\' becomes ' and so
on.) Double backslashes (\\) are made into a single backslash (\)."
I think an ob_handler should be designed to handle output.
Not create (output), nor send emails.
I think the workaround is the other way around hehe
It's the way you want it to work that is a workaround, since there is
probably a better way to do it.
-I agree, print_r($var, true) should work but
Hi
I think it should be constructor's job to set up an instance with the
defaults. (no need for static in this case)
Am i missing something?
Hans Lellelid wrote:
Hi all,
I have a pattern I'm trying to implement in PHP5 using a class that
could be called statically or non-statically. Perhaps "p
would get access to object data (since find is from the
class, not the object).
And that didn't seem like an elegant way eighter hehe
Probably there are other ways...
I should have waited for other replies, shut up and read hehe, but i
fail that from time to time...
Hans Lellelid wrote:
Andre
