Did you recompile PHP completely after you changed the struct? If
not, it's very simple. When you insert a new variable into the middle
of the structure, all the subsequent variables are shifted down. The
ones that used to be at a certain offset can no longer be found there
by the code in p
Perhaps this is the obvious answer, but I'm pretty sure a fair number of
structures used in the engine are, memory-space wise, portions of larger
structures defined elsewhere. This allows the larger structure to be
type-cast to a smaller structure for certain operations easily. It is
possible that
Today I've been debugging a segfault with my namespace patch until I found
that the problem was simply the placement of a variable in a struct. I
still don't see the logic behind it, but I got the segfault both in Windows
2000 and Linux (FC3). The steps to reproduce this segfault are very simple
(u
The attached patch includes variable class name support (test file has also
been updated). To clarify for the benefit of others, this means that the
code below will work. Note that imports are still done on "file-level"
scope, even at runtime, so you can only create objects using variable
import cl
David Zülke writes:
> I don't care about the thousands of idiots out there who are too
> dumb to avoid security leaks.
You don't have to be very dumb to create a whopping big security hole.
It should be *hard* to create a security lapse which causes hostile
code to run on your server. 'include
Guys,
I definitely think that the path to 5.1 currently has to focus on PDO and
the ZE stabilizing. I plan to release Beta 3 hopefully tomorrow (a bit late
because I'm still waiting for some PDO fixes Wez wants to make). Commiting
a new Date extension at this point is definitely high risk. Der
On Mon, 11 Jul 2005, Derick Rethans wrote:
> On Mon, 11 Jul 2005, Pierre-Alain Joye wrote:
>
> > On Mon, 11 Jul 2005 10:16:45 -0700
> > Andrei Zmievski <[EMAIL PROTECTED]> wrote:
> >
> > > Can we please wrap up the whole OO/non-OO discussion and just fix
> > > the damn ext/date so that it works
Derick Rethans wrote:
On Mon, 11 Jul 2005, Pierre-Alain Joye wrote:
On Mon, 11 Jul 2005 10:16:45 -0700
Andrei Zmievski <[EMAIL PROTECTED]> wrote:
Can we please wrap up the whole OO/non-OO discussion and just fix
the damn ext/date so that it works as advertised? The rest can be
done later. L
Hi Gabor,
I managed to salvage it from the depth's of phpweb's cvs attic :)
Edin
- Original Message -
From: "Gabor Hojtsy" <[EMAIL PROTECTED]>
To: "PHP Developers Mailing List"
Sent: Monday, July 11, 2005 7:31 PM
Subject: [PHP-DEV] PHP 4.0.0 binary missing from museum.php.net
Hi,
On Mon, 11 Jul 2005, Pierre-Alain Joye wrote:
> On Mon, 11 Jul 2005 10:16:45 -0700
> Andrei Zmievski <[EMAIL PROTECTED]> wrote:
>
> > Can we please wrap up the whole OO/non-OO discussion and just fix
> > the damn ext/date so that it works as advertised? The rest can be
> > done later. Let's not h
On Mon, 11 Jul 2005 10:16:45 -0700
Andrei Zmievski <[EMAIL PROTECTED]> wrote:
> Can we please wrap up the whole OO/non-OO discussion and just fix
> the damn ext/date so that it works as advertised? The rest can be
> done later. Let's not hold up RC1 unless really necessary.
It's not a stopping fo
>>Could someone responsible look into this bug?
>> http://bugs.php.net/33646
>>
>>PHP 4.0.0. is an important piece of history, so it is better to keep it
>>available IMHO :)
>
> It's tagged in CVS. So just do:
>
> cvs -d:pserver:[EMAIL PROTECTED]:/repository co -r php_4_0_0 php-src
>
> To get
Hello Andrei,
1
Monday, July 11, 2005, 7:16:45 PM, you wrote:
> Can we please wrap up the whole OO/non-OO discussion and just fix the
> damn ext/date so that it works as advertised? The rest can be done
> later. Let's not hold up RC1 unless really necessary.
> -Andrei
> On Jul 8, 200
Gabor Hojtsy wrote:
> Hi,
>
> Could someone responsible look into this bug?
> http://bugs.php.net/33646
>
> PHP 4.0.0. is an important piece of history, so it is better to keep it
> available IMHO :)
>
> Regards,
> Gabor Hojtsy
>
It's tagged in CVS. So just do:
cvs -d:pserver:[EMAIL PROTEC
Hi,
Could someone responsible look into this bug?
http://bugs.php.net/33646
PHP 4.0.0. is an important piece of history, so it is better to keep it
available IMHO :)
Regards,
Gabor Hojtsy
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.
Can we please wrap up the whole OO/non-OO discussion and just fix the
damn ext/date so that it works as advertised? The rest can be done
later. Let's not hold up RC1 unless really necessary.
-Andrei
On Jul 8, 2005, at 1:06 PM, Marcus Boerger wrote:
Hello Derick,
Friday, July 8, 2005, 2:31:1
Hello.
I've translated PHP/PEAR documentation into Japanese. Now I have a karma
for phpdoc-ja, but not for peardoc.
Dose anyone give me a karma for peardoc ?
--
Hideyuki Shimooka
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
Hello!
The PHP Development Team would like to announce the immediate release of
PHP 4.4.0. This is a maintenance release that addresses a serious memory
corruption problem within PHP concerning references. If references were
used in a wrong way, PHP would often create memory corruptions which
Hi,
Are there any plans for an interval/date span/duration type of object?
It would be especially nice to have something like postgresql interval
and XML Schema duration datatype where there are additional fields for
months and years, not just the plain old unsurprising
days,hours,minutes,seconds
PHP 5 Bug Database summary - http://bugs.php.net
Num Status Summary (328 total including feature requests)
===[*General Issues]==
27372 Verified parse error loading browscap.ini at apache startup (new parser
required)
===
PHP 4 Bug Database summary - http://bugs.php.net
Num Status Summary (654 total including feature requests)
===[*Configuration Issues]
33636 Open max_execution_time from php.ini ignored
===[A
21 matches
Mail list logo
