hi Anthony,
On Wed, May 2, 2012 at 1:37 PM, Anthony Ferrara wrote:
> I voted for the ability to use an expression for isset() as well,
> since I agree with Ferenc, it's a matter of consistency. Sure, the
> use-case for isset() is definitely weaker than for empty(),
No, it is not about consiste
On 05/01/2012 11:40 AM, Larry Garfield wrote:
On 5/1/12 10:01 AM, Paul Reinheimer wrote:
Hi All,
Unfortunately, you've ignored Uwe's e-mail... The problem is not the
PHP
version; the problem is that you're buffering unlimited amounts of
data.
Check your configuration and make sure ob_get_lev
On Wed, May 2, 2012 at 5:23 AM, C.Koy wrote:
> On 5/1/2012 9:11 PM, Galen Wright-Watson wrote:
>
>> On Thu, Apr 26, 2012 at 3:45 AM, C.Koy wrote:
>>
>> As of 5.3.0 this bug does not exist for function names. Only classes and
>>> interfaces.
>>>
>>>
>>> Turns out, if you cause a function to be
Anyone have any help with this?
$1 of the first T_ISSET is matching against "\n\t\tisset {..." (... being the
rest of the set body through to the end of the script.
-Original Message-
From: Clint Priest [mailto:cpri...@zerocue.com]
Sent: Wednesday, April 25, 2012 10:41 PM
To: internals
On 5/1/2012 9:11 PM, Galen Wright-Watson wrote:
On Thu, Apr 26, 2012 at 3:45 AM, C.Koy wrote:
As of 5.3.0 this bug does not exist for function names. Only classes and
interfaces.
Turns out, if you cause a function to be called dynamically by (e.g.) using
a variable function, the bug will su
On Wed, May 2, 2012 at 11:43 AM, Pierre Joye wrote:
> hi,
>
> On Wed, May 2, 2012 at 11:36 AM, Ferenc Kovacs wrote:
>
> > $foo=null;
> > var_dump(isset($foo)); //prints bool(false)
>
> No offset meant, but it is totally expected and well known, and as far
> as I remember documented too. Assignin
Pierre,
On Wed, May 2, 2012 at 5:43 AM, Pierre Joye wrote:
> hi,
>
> On Wed, May 2, 2012 at 11:36 AM, Ferenc Kovacs wrote:
>
>> $foo=null;
>> var_dump(isset($foo)); //prints bool(false)
>
> No offset meant, but it is totally expected and well known, and as far
> as I remember documented too. Ass
On Wed, May 2, 2012 at 11:43 AM, Pierre Joye wrote:
> hi,
>
> On Wed, May 2, 2012 at 11:36 AM, Ferenc Kovacs wrote:
>
>> $foo=null;
>> var_dump(isset($foo)); //prints bool(false)
>
> No offset meant,
lapsus :) s,offset,offense,
--
Pierre
@pierrejoye | http://blog.thepimp.net | http://www.li
hi,
On Wed, May 2, 2012 at 11:36 AM, Ferenc Kovacs wrote:
> $foo=null;
> var_dump(isset($foo)); //prints bool(false)
No offset meant, but it is totally expected and well known, and as far
as I remember documented too. Assigning NULL to a variable unsets it
(so to say).
>> empty() on the other
On Wed, May 2, 2012 at 11:10 AM, Pierre Joye wrote:
> hi,
>
> On Wed, May 2, 2012 at 10:46 AM, Laruence wrote:
>
> >so I think if you want to change empty, you should also change isset.
>
> An expression is not set per se. isset goals, by design, from the very
> 1st day, is to test the exist
On Wed, 2012-05-02 at 13:27 +0800, Laruence wrote:
> On Wed, May 2, 2012 at 1:16 PM, Yader Hernandez
> wrote:
> > On Tue, May 1, 2012 at 8:46 PM, Yader Hernandez
> > wrote:
> >
> >> Hello,
> >>
> >> I was wondering how to create a new object from a function call?
> >>
> >> By this I mean if I call
hi,
On Wed, May 2, 2012 at 10:46 AM, Laruence wrote:
> so I think if you want to change empty, you should also change isset.
An expression is not set per se. isset goals, by design, from the very
1st day, is to test the existence of a variable and a variable only.
empty() on the other hand,
On Mon, Apr 30, 2012 at 3:50 PM, Patrick ALLAERT wrote:
> Hi,
>
> 2012/4/12 Nikita Popov :
>> PS: I added isset() too, to address the consistency concerns mentioned on
>> IRC.
>
> I would have voted +1 if it didn't contain the isset() change. None of
> the examples used in the isset_with_expr.php
13 matches
Mail list logo
