Thanx guys for the advices
Respect...
Ante
Marcus Boerger wrote:
Hello AnteD,
Friday, May 13, 2005, 1:29:36 PM, you wrote:
Hi guys...
Yes I know that this is a small function and yes I know it can be
copy-paste with every new project you do but from the first day I've
been using
On Mon, 16 May 2005, George Schlossnagle wrote:
On May 16, 2005, at 3:16 PM, Blake Matheny wrote:
Attached is a small patch that allows for a custom error handler to be used
instead of php_log_err. This is useful for custom logging of error types
that can't be handled with a user-space
Is there anything incorrect/wrong with the solution I proposed? I
realize that a custom extension would also work, but there are several
advantages to doing it the way I implemented it
- No need to add an extension every time you upgrade PHP
- No additional patching (which an extension
On May 17, 2005, at 8:04 AM, Blake Matheny wrote:
Is there anything incorrect/wrong with the solution I proposed? I
realize that a custom extension would also work, but there are
several advantages to doing it the way I implemented it
- No need to add an extension every time you upgrade PHP
On 5/17/05, Blake Matheny [EMAIL PROTECTED] wrote:
- No need to add an extension every time you upgrade PHP
But you still need to write a custom shared library, so this is not
such a great point.
- No additional patching (which an extension essentially requires)
But you still need to write a
After George's comments, I think I'll just write up an extension and
throw it out there. I can still support a script:,file:,socket:,sql:
convention for naming and meet all of my requirements. Thanks for the
feedback.
-Blake
Wez Furlong wrote:
On 5/17/05, Blake Matheny [EMAIL PROTECTED] wrote:
You could submit your extension to http://pecl.php.net if you'd like
to encourage others to make use of it.
--Wez.
On 5/17/05, Blake Matheny [EMAIL PROTECTED] wrote:
After George's comments, I think I'll just write up an extension and
throw it out there. I can still support a
Hi,
unserialize() cannot unserialize objects whose names contain anything except
a-z, 0-9 and _, the parser allows those, though.
Example
===
$ cat unserialize.php
?php
class Über { }
var_dump(unserialize(serialize(new Über(;
?
Expected behaviour
==
$ php
On Tue, 17 May 2005, Timm Friebe wrote:
Fix
===
Allow anything the parser allows, [a-zA-Z_\x7f-\xff][a-zA-Z0-9_\x7f-\xff]*
Do you have a patch? :)
regards,
Derick
--
Derick Rethans
http://derickrethans.nl | http://ez.no | http://xdebug.org
--
PHP Internals - PHP Runtime Development
Hi,
Fix
===
Allow anything the parser allows,
[a-zA-Z_\x7f-\xff][a-zA-Z0-9_\x7f-\xff]*
Do you have a patch? :)
Sorry, no, I'm working under Windows at the moment *without* any development
tools installed except for cygwin, and IIRC PHP won't build with just that
(meaning I couldn't
Is it documented anywhere what the allowed chars are..?
(I couldn't find it anywhere but sources :)
--Jani
On Tue, 17 May 2005, Timm Friebe wrote:
Hi,
unserialize() cannot unserialize objects whose names contain anything except
a-z, 0-9 and _, the parser allows those, though.
Example
11 matches
Mail list logo
