At 10:29 AM 8/20/2004 +0800, Alan Knowles wrote:
Andi Gutmans wrote:
I actually don't think it's the right approach. ext/overload has always
been experimental and it doesn't make sense to start putting such a hack
into the engine.
Normally that would make sense, but the change is realitively min
Andi Gutmans wrote:
I actually don't think it's the right approach. ext/overload has
always been experimental and it doesn't make sense to start putting
such a hack into the engine.
Normally that would make sense, but the change is realitively minor, and
it would reduce the necessity to upgrade
Yes we might.
But first we have to check this is stable and secondly I have to do some
research and see if there are other reasons the opcodes might not be
re-entrant.
Andi
At 02:32 AM 8/20/2004 +0100, Steph wrote:
Not clearer to me :)
If this was a big reason for reverting __toString() for 5.0.
Not clearer to me :)
If this was a big reason for reverting __toString() for 5.0.0, does it mean
we're going to see it again soon as a result of this change?
> -Original Message-
> From: Andi Gutmans [mailto:[EMAIL PROTECTED]
> Sent: 20 August 2004 00:53
> To: Sterling Hughes
> Cc: Andi G
yep, that's right.
On Fri, 20 Aug 2004 11:06:33 +1000, Dave Barr <[EMAIL PROTECTED]> wrote:
> Ilia Alshanetsky wrote:
>
> > iliaa Thu Aug 19 20:55:56 2004 EDT
> >
> > Modified files:
> > /php-src/ext/curl interface.c
> > Log:
> > Added more missing cURL options.
> >
> > + RE
Ilia Alshanetsky wrote:
iliaa Thu Aug 19 20:55:56 2004 EDT
Modified files:
/php-src/ext/curl interface.c
Log:
Added more missing cURL options.
+ REGISTER_CURL_CONSTANT(CURL_TIMECOND_IFMODSINCE);
+ REGISTER_CURL_CONSTANT(CURL_TIMECOND_IFUNMODSINCE);
+ REGISTER_C
Hey,
No it's actually a bigger change than just being in the opcode as opposed
to the end of the opcode. Actually, it would take least one more opcode
execution for the garbage to run. This is the reason why destructors or
resource dtor's would not always be called right away. Now if the garbage
Hello,
+1 on the array parameter. It's flexible, easy to document (as dan put
it), and should accommodate future options.
Also, throwing E_NOTICES would be good to notify you if you mis-type
something, and they can always be suppressed if you want to send an
"unsupported" option.
--
Best
Andi Gutmans wrote:
Not exactly because clean_garbage() was also inline.
Sure, but it was at the end of the opcode, this moves it into the
FREE_OP macro, as opposed to marking (+ sweeping ;) or something else,
right? I'm not against that change in any respect, as I mentioned, I'm
a big +1, jus
I actually don't think it's the right approach. ext/overload has always
been experimental and it doesn't make sense to start putting such a hack
into the engine.
You can easily change the code to use conditional includes and therefore,
your PHP 4 version won't be compiled under PHP 5.
Do you kno
Not exactly because clean_garbage() was also inline.
At 01:28 PM 8/19/2004 -0700, Sterling Hughes wrote:
Andi Gutmans wrote:
andiThu Aug 19 16:03:06 2004 EDT
Modified files:
/ZendEngine2 zend_compile.h zend_execute.c Log:
- Stop using garbage. Please let me know if you find any bu
Andi Gutmans wrote:
andiThu Aug 19 16:03:06 2004 EDT
Modified files:
/ZendEngine2 zend_compile.h zend_execute.c
Log:
- Stop using garbage. Please let me know if you find any bugs resulting
- of this patch (very likely). (Dmitry, Andi)
This patch seems to move
Hi David,
mail() and imap_mail() both call's the internal function TSendMail(). This
is the function that generates the error. the imap version does some
additional chacks for headers. I'll take a look to see if we can make the
error message more informative.
- Frank
> ok thanks. but still, how
> Could you share some more infos about that project?
sure
the project itself is my university thesis, its topic might clear some
things: 'Hive -distributed server for message-driven componental PHP
applications'. main idea is to be able to create php applications in
RAD-way. for this to be possi
Hello Robert,
Thursday, August 19, 2004, 10:29:31 AM, you wrote:
>>> Is this worth further discussion?
>>
>> Not before until we have an application server and php scripts that
>> are designed to run for several months. And even then we would also
>> need improved Reflection support and conatiner
On Thu, 19 Aug 2004 [EMAIL PROTECTED] wrote:
> Yuck! That seems kind of nasty to have to downgrade an application. (I'm
> tracking Debian unstable.)
apt-get install flex-old
> Any chance that the flex-generated C files could
> be distributed in cvs and the Makefile modified to not try to gener
Derick Rethans <[EMAIL PROTECTED]> writes:
> On Wed, 18 Aug 2004 [EMAIL PROTECTED] wrote:
>
>> I'm trying to compile PHP from cvs, but it barfs while trying to generate
>> zend_language_scanner.c from zend_language_scanner.l. The problem is in the
>> specified skeleton file: flex.skl, and it seem
Attached (hopefully) should be a fix for bug #29716, allowing 3
arguments for __call, but emitting a E_STRICT error.
This is needed to enable simple BC wrappers to be written for code
wanting to use overload in PHP4.
BTW: Notes on current CVS
flex 2.5.31 currently reports
flex: fatal internal e
Ilia Alshanetsky wrote:
iliaa Wed Aug 18 17:27:25 2004 EDT
Modified files:
/php-src/ext/curl interface.c
Log:
Fixed bug #29727 (Added missing CURL authentication directives).
[snip]
+
+#if LIBCURL_VERSION_NUM > 0x070a06 /* CURLOPT_PROXYAUTH is available since curl
At 12:21 19/08/2004, Sascha Schumann wrote:
On Thu, 19 Aug 2004, Rasmus Lerdorf wrote:
On Thu, 19 Aug 2004, Hartmut Holzgraefe wrote:
Alan Knowles wrote:
- compile time hooking (no dynamic goto targets)
That kind of makes them useless for writing parsers, which was one of
the justifications of
On Thu, 19 Aug 2004, Rasmus Lerdorf wrote:
On Thu, 19 Aug 2004, Hartmut Holzgraefe wrote:
Alan Knowles wrote:
- compile time hooking (no dynamic goto targets)
That kind of makes them useless for writing parsers, which was one of
the justifications of them.
How that? C doesn't have dynamic goto
>> Is this worth further discussion?
>
> Not before until we have an application server and php scripts that
> are designed to run for several months. And even then we would also
> need improved Reflection support and conatiner support and so on and
> so on.
don`t you think that lacking this destr
Rasmus Lerdorf wrote:
Alan Knowles wrote:
How that? C doesn't have dynamic goto targets either
but still its used for parsing lot ...
That depends on what you consider C.
Try compiling this with your favourite C compiler:
Every day you lern something new ...
looks like i'm already done with that f
On Thu, 19 Aug 2004, Hartmut Holzgraefe wrote:
> Alan Knowles wrote:
> >
> >>- compile time hooking (no dynamic goto targets)
> >>
> >>
> > That kind of makes them useless for writing parsers, which was one of
> > the justifications of them.
>
> How that? C doesn't have dynamic goto targets ei
At 08:32 19/08/2004, Sara Golemon wrote:
> Well, some time ago I wrote a small functions, that does exactly the same:
>
> PHP_FUNCTION(unregister_class)
> {
*snip*
Barring some stylectic differences and a check to make sure it's not an
internal class, that's precisely what I gave sean in
shiva_dest
if you look at the bison/flex, they both use switch/case - the parsers I
use, both generate code like this, however they ended up using variable
functions, as even the overhead of the function calls is faster than the
large switch/case called repeatidly.. (this is ideally what dynamic
goto's c
At 04:28 19/08/2004, Hartmut Holzgraefe wrote:
Sebastian Bergmann wrote:
Exceptions are not an OOP feature per-se. They are a means for out-of-
band error signalling. (Of course they use objects for that which could
be regarded as a turn-off by non-OOP-eople :-)
they can also be a turn-off for p
On Wed, 18 Aug 2004 [EMAIL PROTECTED] wrote:
> I'm trying to compile PHP from cvs, but it barfs while trying to generate
> zend_language_scanner.c from zend_language_scanner.l. The problem is in the
> specified skeleton file: flex.skl, and it seems to be dying near the beginning
> on the first '%
Alan Knowles wrote:
- compile time hooking (no dynamic goto targets)
That kind of makes them useless for writing parsers, which was one of
the justifications of them.
How that? C doesn't have dynamic goto targets either
but still its used for parsing lot ...
--
Hartmut Holzgraefe <[EMAIL P
29 matches
Mail list logo
