Hi all,
2013/7/21 Sherif Ramadan
> The problem is I'm not sure where this type of information should be
> documented. It makes sense to put this on the increment/decrement operators
> page, but doesn't seem appropriate the operator precedence page. So to make
> sure we're all in agreement I'm su
After some digging and a little more thought I find that removing this
comment from the example in the docs at
www.php.net/language.operators.precedence does indeed cause more harm than
good. So I'm definitely wrong in saying that it should be removed.
However, I would like to acknowledge the conf
Hi!
> I agree that we should not rush to commit changes in the midst of
> on-going discussion. However, I have to just add to this notion of
> undefined behavior that by your definition ALL of PHP is undefined
> behavior. Everything we do is an implementation detail. What
This is certainly not tr
On Sat, 2013-07-20 at 10:31 +0100, Arpad Ray wrote:
> I agree this is a largely pointless can of worms, but here's my POC from
> yesterday in case anyone wants to play with it:
> https://gist.github.com/arraypad/6044439
*If* we want to provide a simple function for easy printing for
callbacks and
On Sat, 2013-07-20 at 14:28 +1000, Ryan McCue wrote:
> Sara Golemon wrote:
> > Well, now... to be fair... You could make them functions and use the same
> > parser trick the backtick operator uses. to map the non-parenthesized
> > versions feels messy though. I'd just hate to get stuck with a
On 07/20/2013 08:00 AM, Sherif Ramadan wrote:
> While this is very true it's also a matter of discretion, because the
> language doesn't clearly define a lot of things. In fact, one can argue
> that there is no language definition at all since PHP doesn't even have a
> spec. Though I'm trying to ta
Hi all,
Explanation for undefined behaviors.
===
// If a side effect on a variable is unsequenced relative to another
// side effect on the same variable, the behavior is undefined.
$i = 1;
$i = ++$i + $i++; // undefined behavior
$i = $i++ + 1; // undefined behavior (bu
On Sat, Jul 20, 2013 at 9:24 AM, Lester Caine wrote:
> Stas Malyshev wrote:
>
>> Is there a reason that echo/print couldn't be implemented as functions
>>> >with some sort of backwards compatibility layer? isset/etc make sense to
>>>
>>
> Yes, the reason is not fixing what isn't broken:)
>>
>
>
Hi!
On Jul 20, 2013 4:25 AM, "Jan Ehrhardt" wrote:
>
> Jan Ehrhardt in php.internals (Sat, 20 Jul 2013 03:12:19 +0200):
> >As far as I remember from earlier today, VC10 stumbled over the same
> >unresolved externals. I will check that and will only report it if VC10
> >does not stumble.
>
> VC10
Stas Malyshev wrote:
Is there a reason that echo/print couldn't be implemented as functions
>with some sort of backwards compatibility layer? isset/etc make sense to
Yes, the reason is not fixing what isn't broken:)
And perhaps introducing 'black holes' like the one created when stopped work
On Sat, Jul 20, 2013 at 3:37 AM, Stas Malyshev wrote:
> Hi!
>
> > I cannot believe this is true now, but I ask list before I fix doc.
>
> I don't think there's something that needs to be fixed. "Undefined"
> means "it depends on implementation and we do not want to commit to a
> specific behavior
Hi Stas,
2013/7/20 Stas Malyshev
> Hi!
>
> >> If there aren't comments, I'll rewrite the example.
> >>
> >>
> >> There were comments. I explicitly told you that that the behavior is
> > defined as undefined. You CHOSE to ignore that comment. You CHOSE to
> > break the documentation.
>
> Besid
Hi!
> Is there a reason that echo/print couldn't be implemented as functions
> with some sort of backwards compatibility layer? isset/etc make sense to
Yes, the reason is not fixing what isn't broken :)
--
Stanislav Malyshev, Software Architect
SugarCRM: http://www.sugarcrm.com/
(408)454-6900 ex
Hi!
>> If there aren't comments, I'll rewrite the example.
>>
>>
>> There were comments. I explicitly told you that that the behavior is
> defined as undefined. You CHOSE to ignore that comment. You CHOSE to
> break the documentation.
Besides that, asking for comments and committing the same d
Hi!
> I cannot believe this is true now, but I ask list before I fix doc.
I don't think there's something that needs to be fixed. "Undefined"
means "it depends on implementation and we do not want to commit to a
specific behavior here because implementations may change". This is a
fair warning ag
15 matches
Mail list logo
