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.
Bec
Hi Derick,
I don't think we should get rid of it, or add a notice/message/whatever.
Because this:
http://pastebin.com/d6e055957
could not be done without call time pass by ref right now. So unless
that's fixed, we shouldn't deprecate it.
Hm. Actually those 'expected values' are wrong because
Hello Steph,
I am all for it: Making sure PHP's 5.3 default is OFF and issueing a warning
when turning on starting with 5.3.
marcus
Wednesday, May 21, 2008, 3:13:04 PM, you wrote:
> I looked into it again (and found things I didn't know before). This one's
> bugging me enough that I brave
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.
Because this:
http:/
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'm all for it.
regards,
Derick
--
PHP Internals - PHP Runtime Development Mailing List
To u
Hi!
1) At call time, nothing significes what is the caller passing, the
syntax is the same for passing reference or passing value, so it's prone
There's no such thing as "passing reference or passing value". Same
thing is always passed - zval. Only thing changing is does the function
intend
Hi,
There are three purposes:
1) At call time, nothing significes what is the caller passing, the syntax
is the same for passing reference or passing value, so it's prone to
confusion. You're passing something which *may* or *may not* be modified if
taken as a reference. Quick, is the variab
Hi Stan,
There is a use case for the function allowing *explicitly* call-time pass
by reference, because the function works both ways in subtly different
ways.
This RFC isn't about whether or not this behaviour should be deprecated. It
simply recommends that a warning be thrown by default in
Hi,
Actually PHP ignores default values on parameters followed by required ones.
You can't fetch the default value even via Reflection.
This is easily detected at compile time so I wonder why the compiler doesn't
warn.
Regards,
Stan Vassilev
what stops you from declaring:
function someFu
On Thu, May 22, 2008 at 2:51 PM, LEW21 <[EMAIL PROTECTED]> wrote:
> 2008/5/22, Alexey Zakhlestin <[EMAIL PROTECTED]>:
>> On Wed, May 21, 2008 at 10:46 PM, LEW21 <[EMAIL PROTECTED]> wrote:
>> > Sometimes call time pass by reference is useful, for example when you
>> > want to make it possible to o
2008/5/22, Alexey Zakhlestin <[EMAIL PROTECTED]>:
> On Wed, May 21, 2008 at 10:46 PM, LEW21 <[EMAIL PROTECTED]> wrote:
> > Sometimes call time pass by reference is useful, for example when you
> > want to make it possible to omit an param (normally passed by
> > reference) by setting null. With
Hi,
There is a use case for the function allowing *explicitly* call-time pass by
reference, because the function works both ways in subtly different ways.
I have some libraries where I had to have variations of the functions like
"AbcByRefr()" and "Abc()", because of this inflexibility.
In
On Wed, May 21, 2008 at 10:46 PM, LEW21 <[EMAIL PROTECTED]> wrote:
> Sometimes call time pass by reference is useful, for example when you
> want to make it possible to omit an param (normally passed by
> reference) by setting null. With no call time pass by reference,
> programmers are required to
Sometimes call time pass by reference is useful, for example when you
want to make it possible to omit an param (normally passed by
reference) by setting null. With no call time pass by reference,
programmers are required to write:
$null = null;
foo($null);
Deleting it isn't a good idea, it shoul
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
It has:
| Proposal
|
| Switch allow_call_time_pass_reference off by default in PHP_5_3
| branch. At present there is no
For anyone else who doesn't read to the end...
Anyway, my opinion is clear on that one: shoot that dead cow. It's
been deprecated for years, and you should declare your function
prototypes with the param by ref anyway if you need it.
All I'm asking is that we throw a warning by default in 5_3,
Is it me, or the wiki post talks about param and return by ref?
Return by ref is not related to call-time pass by ref, is it?
See zend_compile.c.
Anyway, my opinion is clear on that one: shoot that dead cow. It's
been deprecated for years, and you should declare your function
prototypes with
Hello Steph,
Is it me, or the wiki post talks about param and return by ref?
Return by ref is not related to call-time pass by ref, is it?
Anyway, my opinion is clear on that one: shoot that dead cow. It's
been deprecated for years, and you should declare your function
prototypes with the param
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
- Steph
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
19 matches
Mail list logo
