How many date formatting functions do we need?
-Andrei
Zeev Suraski wrote:
> I've been away from email for the last couple of weeks - read through the
> timezone thread, and didn't really see a conclusion.
>
> My suggestion is to restore the old code in its entirely, and introduce
> the
> new imp
On Mon, 10 Oct 2005 20:29:32 +0200 (CEST)
[EMAIL PROTECTED] (Derick Rethans) wrote:
> On Mon, 10 Oct 2005, Stanislav Malyshev wrote:
>
> > IA>>It was MFHed to 5.1
> >
> > Why not to 5.0?
>
> 5.0 is dead? :)
5.1 is released? :)
--
PHP Internals - PHP Runtime Development Mailing List
To unsubs
> I agree that allowing "=& new" and disallowing "return new"
> by reference is inconsistent.
I'm so stubborn with this one because there might be good reasons if
you're the mechanic lying under the car fixing the engine, but it does
not make any sense if you just want to drive the car :)
> But
Hello David,
Thursday, October 6, 2005, 9:49:35 AM, you wrote:
> Thanks! That was very useful information. Had to go with the #3a
> solution as I need to be compatible with PHP4.
> I still have some problems with my extension though. The extension
> maintains a module global C++ std::map alloc
On Mon, 10 Oct 2005, Stanislav Malyshev wrote:
> IA>>It was MFHed to 5.1
>
> Why not to 5.0?
5.0 is dead? :)
Derick
--
Derick Rethans
http://derickrethans.nl | http://ez.no | http://xdebug.org
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/
IA>>It was MFHed to 5.1
Why not to 5.0?
--
Stanislav Malyshev, Zend Products Engineer
[EMAIL PROTECTED] http://www.zend.com/ +972-3-6139665 ext.115
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
It was MFHed to 5.1
Ilia
Stanislav Malyshev wrote:
> Is there any reson why this patch:
>
> http://cvs.php.net/diff.php/php-src/ext/standard/php_incomplete_class.h?r1=1.15&r2=1.16&ty=u
>
>
> wasn't MFH'ed to older branches? I.e., was it done intentionally or it
> was just an omission?
--
PHP
Is there any reson why this patch:
http://cvs.php.net/diff.php/php-src/ext/standard/php_incomplete_class.h?r1=1.15&r2=1.16&ty=u
wasn't MFH'ed to older branches? I.e., was it done intentionally or it was
just an omission?
--
Stanislav Malyshev, Zend Products Engineer
[EMAIL PROTECTED] http://w
I agree that allowing "=& new" and disallowing "return new" by reference is
inconsistent.
But PHP4 is stable tree. We don't like different versions with different
behavior.
In PHP5 "=& new" is deprecated, so I don't see any reason to introduce
"return new" by ref in PHP5.
Dmitry.
> -Origina
On Sun, 9 Oct 2005, Nuno Lopes wrote:
> > I'm not sure if all the patches are commited as for now, but it still
> > doesn't work for me. First, IDT setting still returns unknown timezone,
> > second, now PHP crashes in:
> >
> > 0x08095bcd in timelib_tzinfo_dtor (tz=0x0) at
> > php5/ext/date/lib/ti
So that means that all the zval * I store in my map simply point to
invalid memory once the request is completed? Well, that would explain
some of the strange behaviour I have observed (such as string changing
content between requests).
Yep.
The solution to this would be to allocate the
zval s
On Mon, 10 Oct 2005, Matthias Pigulla wrote:
> PS. Anyone ever thought about explaining the whole reference-related
> decisions on the upcoming International PHP Conference? Maybe that could
> help to gain understanding as to why the changes were necessary... Maybe
> also give a statement as to po
> Von: Derick Rethans [mailto:[EMAIL PROTECTED]
> On Sat, 8 Oct 2005, Matthias Pigulla wrote:
> > The point is that this requires really unlogic and silly
> > workarounds
> > like 'return $tmp =& new Foo()'. That forces people to touch stable
> > codebases; I find it comprehensible that they
On Mon, 10 Oct 2005, Stanislav Malyshev wrote:
> NL>>This patch should fix the segfault:
> NL>>http://mega.ist.utl.pt/~ncpl/php_date_segf.txt
>
> Any reason it's not in 5.1 CVS?
Yes, I didn't have time to look at it yet. I've other things to do :)
Derick
--
Derick Rethans
http://derickrethans
On Sat, 8 Oct 2005, Matthias Pigulla wrote:
> The point is that this requires really unlogic and silly workarounds
> like 'return $tmp =& new Foo()'. That forces people to touch stable
> codebases; I find it comprehensible that they feel this is like passing
> the engine internal problems to the p
NL>>This patch should fix the segfault:
NL>>http://mega.ist.utl.pt/~ncpl/php_date_segf.txt
Any reason it's not in 5.1 CVS?
--
Stanislav Malyshev, Zend Products Engineer
[EMAIL PROTECTED] http://www.zend.com/ +972-3-6139665 ext.115
--
PHP Internals - PHP Runtime Development Mailing List
To uns
On Sun, 9 Oct 2005 00:55:45 -0400 (EDT), in php.internals
[EMAIL PROTECTED] (Adam Maccabee Trachtenberg) wrote:
>We seem to be under the impression that the Unicode speed penalty will
>be so harsh that a Unicode-only PHP 6 will be too slow for
>use. However, we don't know that for sure. Yes, it wi
David Olsson wrote:
malloc to allocate memory. This means that my memory allocations using
c++ new should allocate persistent memory chunks. So the
persistent/non-persistent memory issue doesn't explain why my std::map
simply is empty. The fact that it contain zval pointers pointing to
invalid
Normal userspace variables (zvals) are allocated "non-persistently".
This means that, for example, creating a string variable consists of
emalloc() calls:
foo = emalloc(sizeof(zval));
foo->value.str.val = emalloc(sizeof("bar"));
emalloc()'d pointers are forcibly freed between requests (as p
PHP 5 Bug Database summary - http://bugs.php.net
Num Status Summary (375 total including feature requests)
===[*General Issues]==
26771 Suspended register_tick_funtions crash under threaded webservers
==
PHP 4 Bug Database summary - http://bugs.php.net
Num Status Summary (628 total including feature requests)
===[*General Issues]==
25665 Assigned var_dump/print_r hang on NaN and INF
===[Arra
21 matches
Mail list logo
