Michael Wallner wrote:
1. on-the-fly static properties (mike)
I didn't request these
FYI, the names in parenthesis are the person I figured was most likely
to implement the given feature and not who requested it necessarily.
Anyways, a lot of people abuse the comment system on the todo
Hi,
I am not sure whether I should post here or into php-general so feel free to
bug me away ;)
Anyway I have found a difference with ArrayObject::offsetExists between php
5.2.0 and php 5.2.1.
With 5.2.0 ArrayObject::offsetExists will return true if the offsetExists
whether its value is empty
On 9-Feb-07, at 1:49 AM, Lukas Kahwe Smith wrote:
1. on-the-fly static properties (mike)
It was already discussed on the mailing list in the past and declined.
2. 'strict class' to disable dynamic member variable addition
(marcus)
Possible for 5.3, or PHP 6 but definitely not 5.2
Ilia Alshanetsky wrote:
On 9-Feb-07, at 1:49 AM, Lukas Kahwe Smith wrote:
1. on-the-fly static properties (mike)
It was already discussed on the mailing list in the past and declined.
Hmm I will search the archives, but I am not aware that this was declined.
regards,
Lukas
--
PHP
Ilia Alshanetsky wrote:
5. pat3 OpenLDAP C API cleanup patch and pat44 LDAP control
support
The patch is where?
http://marc.theaimsgroup.com/?l=php-devm=115635520414869w=2
I should have mentioned that many of the items have links that are
listed on the PHP 5.2 todo page:
Lukas Kahwe Smith wrote:
Ilia Alshanetsky wrote:
On 9-Feb-07, at 1:49 AM, Lukas Kahwe Smith wrote:
1. on-the-fly static properties (mike)
It was already discussed on the mailing list in the past and declined.
Hmm I will search the archives, but I am not aware that this was declined.
Ilia,
http://devzone.zend.com/node/view/id/1432 is the new PAT directory. I know
it's not very catchy -
http://devzone.zend.com/public/view/tag/Weekly_Summaries will generally find
it.
The top four are dead links at present pending a permissions issue getting
itself resolved. The rest
Hi, I'm looking through the list of security issues listed in the 5.2.1
release notes; trying to work out what the impact of these issues is so
we're able to explain to our users how they are affected.
Could anyone help clarify a few of the items listed?
- Fixed allocation bugs caused by
Joe,
I am reluctant to disclose more information about the particulars of
the issues so soon after the release, without giving a change for
people to upgrade to it first. Once a month or so passes, I'd be
happy to provide you, or anyone else interested with additional
information about
Dear PHP Internals subscribers,
I have two quick questions regarding PHP 5's Reflection API (I apologize if
this isn't the right list to ask):
1) Is there a way to inject a method into a Class such that future
instantiations of that Class will have the method? For example:
Before
On Thu, 8 Feb 2007, Mathieu Gagné wrote:
Hi,
Thanks for the update! Much appreciated.
Is there any chances to get this patch for PHP 4.x too?
Depends a bit on how much of a change it is. If it touches almost no
exsisting code we might want to consider it.
Derick
--
Derick Rethans
On Thu, 8 Feb 2007, Adam Maccabee Trachtenberg wrote:
I read this as saying we're removing the entire ereg extension from
PHP 6. If that's not true, then never mind.
http://www.php.net/~derick/meeting-notes.html#move-ereg-to-pecl
regards,
Derick
--
PHP Internals - PHP Runtime Development
On Fri, 9 Feb 2007, Guilherme Blanco wrote:
Christian Schneider wrote:
Please use plain text mail as your messages are a PITA to read, thanks.
I changed the email to send/recieve messages. Hotmail simply doesn't
accept plain text.
hotmail also fucks up threading :I
regards,
Derick
--
On Fri, 9 Feb 2007, Lukas Kahwe Smith wrote:
Lukas Kahwe Smith wrote:
Ilia Alshanetsky wrote:
On 9-Feb-07, at 1:49 AM, Lukas Kahwe Smith wrote:
1. on-the-fly static properties (mike)
It was already discussed on the mailing list in the past and declined.
Hmm I will
Jim Wilson wrote:
1) Is there a way to inject a method into a Class such that future
instantiations of that Class will have the method? For example:
2) Is there a way to change a method which already exists, as in by
overwriting it with a new function? I'm looking to do the equivalent of
Lukas Kahwe Smith wrote:
Hello,
On the heels of the 5.2.1 release I just wanted to bring up the
following todo items that have been on the 5.x todo lists since ages.
Are these still alive? Have they been done? What would be a sensible
target version?
Especially the on-the-fly static
Hi Jim,
you're searching for runkit ;-)
http://de.php.net/manual/en/ref.runkit.php
johannes
On Fri, 2007-02-09 at 10:18 -0600, Jim Wilson wrote:
Dear PHP Internals subscribers,
I have two quick questions regarding PHP 5's Reflection API (I apologize if
this isn't the right list to ask):
From: Derick Rethans [mailto:[EMAIL PROTECTED]
On Thu, 8 Feb 2007, Adam Maccabee Trachtenberg wrote:
I read this as saying we're removing the entire ereg extension from
PHP 6. If that's not true, then never mind.
http://www.php.net/~derick/meeting-notes.html#move-ereg-to-pecl
From
On that note - is there a formal process in place for deciding what gets
moved from PCEL to 'Optional Extension' and vice-versa? Who has final say
in the matter?
-- Jim
On 2/9/07, LAUPRETRE François (P) [EMAIL PROTECTED] wrote:
From: Derick Rethans [mailto:[EMAIL PROTECTED]
On Thu, 8 Feb
I proposed several times to make the process more formal, with a real RFC
process. It does not
have to be more complex than what the Zend Framework uses. I never had any
reply...
As time passes, I also start to be fed up with these feature removals. I also
start suspecting
some people to have
Is there a PHP/Zend bug-tracking system that can be used to record and
moderate these requests (like a Bugzilla server somewhere)? Or is there a
wiki or forum that that can be devoted to the change-process?
(Sorry for these n00b questions - I'm a long time PHP hacker - but I've only
recently
I think it would be great to have something like a wiki for proposals
and requests for a start.
However, the discussion on these topics shouldn't be moved to the wiki
(- quite annoying); maybe a forum would be adequate.
Problematic: the wiki has to be kept up-to-date with the discussion in
the
Jim Wilson wrote:
Is there a PHP/Zend bug-tracking system that can be used to record and
moderate these requests (like a Bugzilla server somewhere)? Or is there a
wiki or forum that that can be devoted to the change-process?
(Sorry for these n00b questions - I'm a long time PHP hacker - but
Heads up! Installed the latest Win32 binaries of thread-safe PHP 5.2.1
on Win32 Apache and IIS. PHP started crashing (definitely PHP -
php5ts.dll) when I went to access the MyProBB web forum. (Win32 Apache
flat out crashes, IIS bails with HTTP 500 errors).
Forum crashes PHP 5.2.1:
On 2/9/07, Lukas Kahwe Smith [EMAIL PROTECTED] wrote:
you can always file a feature request in a bug report.
It would rapidly be flagged as bogus ;)
Olivier
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
On Fri, 9 Feb 2007, Derick Rethans wrote:
On Thu, 8 Feb 2007, Adam Maccabee Trachtenberg wrote:
I read this as saying we're removing the entire ereg extension from
PHP 6. If that's not true, then never mind.
http://www.php.net/~derick/meeting-notes.html#move-ereg-to-pecl
To confim I'm
On 9.2.2007 18:10 Uhr, Nico Sabbi wrote:
may I re-propose the attached patch? The first time it was ignored, but
the current behaviour of
dom module is extremely annoying
Completely out of context your post, but I was the one who wrote that
part of code, since I was more or less forced to
On 02/09/2007 10:29 PM, Olivier Hill wrote:
On 2/9/07, Lukas Kahwe Smith [EMAIL PROTECTED] wrote:
you can always file a feature request in a bug report.
It would rapidly be flagged as bogus ;)
You didn't even try it, did you?
--
Wbr,
Antony Dovgal
--
PHP Internals - PHP Runtime
On 02/09/2007 11:10 PM, Adam Maccabee Trachtenberg wrote:
On Fri, 9 Feb 2007, Derick Rethans wrote:
On Thu, 8 Feb 2007, Adam Maccabee Trachtenberg wrote:
I read this as saying we're removing the entire ereg extension from
PHP 6. If that's not true, then never mind.
Antony Dovgal wrote:
As far as I understand, the point is that ereg does/can not support
Unicode, therefore we cannot keep it PHP6, which major feature is
Unicode support.
_BUT_ it is possible to use PCRE to emulate ereg, so yes, the existing
code
should continue working.
Well I remember
On 2/9/07, Lukas Kahwe Smith [EMAIL PROTECTED] wrote:
Overall I would say, while painful I do not really see the point in
investing development resources into keeping ereg alive, since its just
a duplication of efforts. Then again I have avoided ereg since PHP4
days. The ereg userbase will be
Olivier Hill wrote:
On 2/9/07, Lukas Kahwe Smith [EMAIL PROTECTED] wrote:
Overall I would say, while painful I do not really see the point in
investing development resources into keeping ereg alive, since its just
a duplication of efforts. Then again I have avoided ereg since PHP4
days. The
On Fri, 09 Feb 2007 22:27:37 +0100, in php.internals
[EMAIL PROTECTED] (Lukas Kahwe Smith) wrote:
Well I remember that Andrei once brought up the idea of an ereg wrapper
around pcre, but IIRC the idea was dropped because there would be tons
of subtle issues from edge cases. So the decision was
Nonetheless the current PCRE functions leads to confusion and
weirdness as long the perl syntax is mixed with php.
I wonder if this more true for people who have used Perl. Personally, I
have never used perl on a daily basis. The PCRE syntax has never caused
me much trouble. But, I can see
This script crashes PHP 5.2.1 everywhere. Command-line and web server
(module and CGI modes). IMO, there's a bug somewhere in str_ireplace().
But it could be also more fundamental with how Zend treats variables.
All that showing data around assigning a variable to itself.
I can reproduce
I can reproduce it. Seems to be off-by-one here:
Z_STRVAL_P(result) = target = safe_emalloc(char_count, to_len, len);
introduced by this patch:
http://cvs.php.net/viewvc.cgi/php-src/ext/standard/string.c?r1=1.445.2.14.2.36r2=1.445.2.14.2.37
If I replace len with len+1, it seems to be OK.
On 02/09/2007 09:40 PM, Thomas Hruska wrote:
?
$Data = Change tracking and management software designed to watch
for abnormal system behavior.\nSuggest features, report bugs, or ask
questions here.;
$Data = str_ireplace(\r\n, br, $Data);
$Data = str_ireplace(\n, br, $Data);
$Data
Fixed in CVS, thanks for the reproduce case.
I think there should be also no check for case_sensitivity earlier.
And we probably need to add testcase for this - our test suite seems to
have missed this bug).
--
Stanislav Malyshev, Zend Products Engineer
[EMAIL PROTECTED]
On 02/10/2007 03:55 AM, Stanislav Malyshev wrote:
Fixed in CVS, thanks for the reproduce case.
I think there should be also no check for case_sensitivity earlier.
And we probably need to add testcase for this - our test suite seems to
have missed this bug).
I will add a test case, but not
Good point. So if the decision is indeed to deprecate ereg, its time to
mark it deprecated. And while we are at it .. lets introduce
E_DEPRECATED as well :)
Please do (Someone. I do realize Lukas can't.)
- Steph
regards,
Lukas
--
PHP Internals - PHP Runtime Development Mailing List
Peter, be that as it may (my fault all of it), the current PCRE
syntax is not going to change.
We'll be wiser when implementing the interface to the ICU regexp
library.
-Andrei
On Feb 9, 2007, at 2:48 PM, Peter Brodersen wrote:
On Fri, 09 Feb 2007 22:27:37 +0100, in php.internals
I guess I missed the part of removing the extension.
I very much agree with using PCRE in the Core instead of ereg() and enabling
PCRE by default.
However, I think it's a bad idea to unbundle ereg. I think a huge amount of PHP
apps depend on ereg() and it would be a real PITA
for our users if we
42 matches
Mail list logo
