Ilia Alshanetsky wrote:
[..]
I would like to ask all developers to voice their opinions of whether it
makes sense to add this to 5.3 or to throw it away (either one is fine
btw).
+1
[..]
- Mark
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit:
Ilia Alshanetsky wrote:
There has been quite a bit of discussion on this list, IRC, developer
meetings, etc... about introduction of type hinting to PHP.
[..]
My hope is that the latest changes will allow this to become a standard
part of PHP.
+1
[..]
- Mark
--
PHP Internals - PHP
Hi list,
The following doesn't strike me as consistent behavior:
$a = new ArrayObject();
$a[foobar] = NULL;
echo (int) isset( $a[foobar] ); // Output: 1
While it's technically correct, I find it confusing. The reason is
probably because of a array_key_exists (or property_exists)
Sorry for bringing an old thread back to life, but imo this needs some
more attention.
Sebastian wrote:
hi,
PHP6 still replaces . with an underscore in variables from outside. this
is an old behavior forced by register globals so i would say its a bug since
. is valid in array keys.
Hannes Magnusson wrote:
On Wed, Nov 12, 2008 at 03:57, Stan Vassilev | FM [EMAIL PROTECTED] wrote:
I don't see it would work with something like
import_request_variables() unless thats removed or extract(), which is
some of the reasons for this replacement feature afair.
There was never a
Stanislav Malyshev wrote:
Hi!
I notice that 5.3 differs from 5.2 in how array_key_exists treats
objects. In 5.2, if the second parameter (array) is allowed to be object
and HASH_OF is applied to it. However, in 5.3 it would produce a warning
requiring an array if object passed to it. Was it
Hannes Magnusson wrote:
On Sun, Jun 1, 2008 at 7:43 PM, Stanislav Malyshev [EMAIL PROTECTED] wrote:
Hi!
use FooBar::In::Some::NameSpace as foo,
SomeOther::Cool:Massive::awesome::space as bar, And::other:namespace
as foobar;
vs
use FooBar::In::Some::NameSpace as foo;
use
Derick Rethans wrote:
On Wed, 21 May 2008, Steph Fox wrote:
I looked into it again (and found things I didn't know before). This one's
bugging me enough that I braved the Wiki:
http://wiki.php.net/rfc/calltimebyref
I don't think we should get rid of it, or add a notice/message/whatever.
Derick Rethans wrote:
On Thu, 17 Apr 2008, Felipe Pena wrote:
Now with both parameter and return value type hints.
For parameter type hints, i have completed the actual implementation
with the leftover php types:
- string (binary string and unicode)
- integer (accepting numeric string too)
-
[EMAIL PROTECTED] wrote:
Hi,
[..]
Request for Comments: Traits for PHP
[..]
If it doesn't affect performance *MUCH* then I'm all for it ! It can
bring better structure for complex designs. Also by reusing, I'm
assuming less memory will be needed for the
Pierre Joye wrote:
Hi,
+1: remove them (as it is now in HEAD)
-1: Restore them and always return FALSE (not 0)
0: I don't care, do what you wish, I never use them anyway
-1
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
Wietse Venema wrote:
I've uploaded a new version of taint support for PHP. You can find
all the files via:
ftp://ftp.porcupine.org/pub/php/index.html
[..]
For examples and details, see the README file, also on-line at:
12 matches
Mail list logo