Of course not (and I know we use import in a few places in ZF) which is why I
want to see whether it makes sense to allow reserved words. The basic parsing
rule would be easy but we need to check how many other areas this might affect.
Wouldn't want to introduce any more inconsistencies. If it e
Andi Gutmans wrote:
> Hi Johannes,
> Our preference would be to stick to "import" because I think the perception
> many will have of "use" is that it also includes files (just based on some
> other languages). That said I agree that compatibility would be an issue
> here. In fact it's even somew
Hi all,
Could someone point me to the message(s) explaining why the executor is
unstable when an exception is thrown in __autoload()?
Thanks,
Greg
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
BTW: Here is the bug that I am referring to:
http://bugs.php.net/bug.php?id=41822
& correction: getcwd() is not an stdio function ;)
Rob Thompson wrote:
> Hi everyone, I just subscribed to this list in hopes of working out some
> PHP bugs that have to do with Solaris.
>
> I've been trying to f
Hi everyone, I just subscribed to this list in hopes of working out some
PHP bugs that have to do with Solaris.
I've been trying to find out some reason why the getcwd() PHP function
fails under some situations under Solaris. Particularly, when some
component of the file path looks like: d--x--x
Hi internals,
another small patch. This time concerning
http://bugs.php.net/bug.php?id=42818. As I'm not a ZendEngine expert I'm
not sure if this is the right place and the right way to fix the bug, but
at least for me this small fix works fine. Maybe somebody who is really
into depth with the eng
i forgot to mention. its against PHP_5_3 and also contains the necessary
adjustments in ext/spl/spl_directory.c
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
Changing 'detect_unicode' disabled as default is a possible solution.
But, it might cause some backward incompatibility issues.
If no one gives any objection within a coupled of days,
I will commit the change ('detect_unicode' will be disabled by default).
Rui
On Thu, 27 Sep 2007 18:37:57 +020
Hi internals,
once again a proposal for a bugfix.
This time concerning http://bugs.php.net/bug.php?id=40501.
As the standard escape character is \\ , but the RFC says ", I added a
optional escape character to the function call as a last parameter.
Furthermore, when the escape character is the sa
Andi Gutmans schrieb:
Our preference would be to stick to "import" because I think the perception many will have of
"use" is that it also includes files (just based on some other languages). That said I agree that
compatibility would be an issue here. In fact it's even somewhat of an issue with
This would be pretty easy, in a hackish way, by adding a whole bunch of
duplicate rules T_FUNCTION T_STRING, T_FUNCTION T_IMPORT, T_FUNCTION
T_NAMESPACE and so on. A more robust way would be to move to lemon/re2c
but I'm not volunteering to do this (yet?)
probably better something like keyword_
Andi Gutmans wrote:
> Hi Johannes, Our preference would be to stick to "import" because I
> think the perception many will have of "use" is that it also includes
> files (just based on some other languages). That said I agree that
> compatibility would be an issue here. In fact it's even somewhat o
Sorry to bother, I have a few questions on this matter.
How will this impact on the SPL ArrayAccess and related interfaces and
objects?
That's the problem with such syntax - one would expect it works with
ArrayAccess and it starts to be complicated...
--
Stanislav Malyshev, Zend Software Arch
Sorry to bother, I have a few questions on this matter.
How will this impact on the SPL ArrayAccess and related interfaces and
objects?
Will there be an interface to this functionality?
If so, how will ranges be passed through to this interface?
Will this be consistent with substr() and array_slice
Hi Johannes,
Our preference would be to stick to "import" because I think the perception
many will have of "use" is that it also includes files (just based on some
other languages). That said I agree that compatibility would be an issue here.
In fact it's even somewhat of an issue with "namespac
It's on my TODO list.
-Andrei
Alexey Zakhlestin wrote:
Here http://www.php.net/~derick/meeting-notes.html#cleanup-for-vs is a
phrase "For both strings and arrays, the [] operator will support
substr()/array_slice() functionality"
will it appear in php5.x (php 5.3)?
--
PHP Internals - PHP R
Stanislav wrote me a very useful reply to my CV questions. I wonder if
anyone has time to give me a quick note on backpatching, and what that
is?
I think backpatching refers to updating past opcodes (i.e. opcodes for
code that was already parsed) when they need something that would be
known on
Alexey Zakhlestin wrote:
Here http://www.php.net/~derick/meeting-notes.html#cleanup-for-vs is a
phrase "For both strings and arrays, the [] operator will support
substr()/array_slice() functionality"
will it appear in php5.x (php 5.3)?
I think since we do have substr/array_slice there's no nee
Patch applied to HEAD / PHP_5_3.
--Jani
On Mon, 2007-08-06 at 09:57 -0400, David Soria Parra wrote:
> Hi internals,
>
> so based on a discussion of php.pecl we thought about using the php_getopt
> for the PHP_FUNCTION(getopt) instead of the system provided getopt. Here
> is the patch for that. H
On 01.10.2007 16:32, Ilia Alshanetsky wrote:
> This was not on the table and the time of the 5.3 discussion, I for
> one think its a bit too much magic.
Yeah, too Perl-ish for me.
--
Wbr,
Antony Dovgal
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www
This was not on the table and the time of the 5.3 discussion, I for
one think its a bit too much magic.
On 1-Oct-07, at 7:30 AM, Alexey Zakhlestin wrote:
Here http://www.php.net/~derick/meeting-notes.html#cleanup-for-vs is a
phrase "For both strings and arrays, the [] operator will support
su
Here http://www.php.net/~derick/meeting-notes.html#cleanup-for-vs is a
phrase "For both strings and arrays, the [] operator will support
substr()/array_slice() functionality"
will it appear in php5.x (php 5.3)?
--
Alexey Zakhlestin
http://blog.milkfarmsoft.com/
--
PHP Internals - PHP Runtime
Hi Robin,
Thank you for catching this issue.
static:: make no sense in compile-time constants.
I've just forbidden it there.
Thanks. Dmitry.
> -Original Message-
> From: Robin Fernandes [mailto:[EMAIL PROTECTED]
> Sent: Friday, September 28, 2007 6:45 PM
> To: internals@lists.php.net
Hi Sebastiann et al.,
On Sun, 2007-09-30 at 18:06 +0200, Sebastian Bergmann wrote:
> When we removed the namespace implementation that was scheduled for
> PHP 5.0 before PHP 5.0's release we kept the T_NAMESPACE and T_USE
> tokens for forward-compatibility.
T_NAMESPACE is new, only T_USE wasn't
Hi,
Stanislav wrote me a very useful reply to my CV questions. I wonder if
anyone has time to give me a quick note on backpatching, and what that
is?
On 9/23/07, Paul Biggar <[EMAIL PROTECTED]> wrote:
> What is backpatching?
> Is it related to compiled variables, or are they different concepts?
>
On 01.10.2007 07:29, Robert Thompson wrote:
> Help debug and fix continuing issues with respect to PHP + Solaris.
> In the position of debugging and fixing Solaris + PHP issues almost
> exclusively for my job.
> In particular, I would like to contribute to code fixes and configuration
> check
PHP 6 Bug Database summary - http://bugs.php.net
Num Status Summary (62 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 (634 total including feature requests)
===[*Programming Data Structures]=
40496 Assigned Test bug35239.phpt still fails (works in PHP 5)
=
28 matches
Mail list logo
