> On one hand, I think it makes sense - nobody really cares where the
> exception was created... But there's one problem here:
>
> try {
> //stuff
> } catch(Exception $e) {
> $logger->log("Oops, exception!");
> throw $e;
> }
>
> If we update file/line here, we lose original exceptio
- Ursprüngliche Message -
> Von: Gustavo Lopes
> An: 'Patrick Schaaf' ; "internals@lists.php.net"
> ; Frank Liepert ; hakre
>
> CC: 'Derick Rethans' ; 'Martin Jansen'
> Gesendet: 21:19 Freitag, 8.Februar 2013
> Betre
SIGN' (U+00B1).
It's an equally incorrect sign for the number 0 as "-" or "+" is incorrect.
Available in internet standards ISO-8859-1 and more as "\xB1" (UTF-8 as
"\xC2\xB1"), FILTER_VALIDATE_INT should reflect hidden dependency of input
encoding here.
My ±0*2 cents here.
-- hakre
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
- Ursprüngliche Message -
> Von: Zeev Suraski
> An: hakre
> CC: internals@lists.php.net
> Gesendet: 15:31 Dienstag, 5.Februar 2013
> Betreff: RE: [PHP-DEV] [RFC] Integrating Zend Optimizer+ into the PHP
> distribution
>
>> > Based on an 18 month
- Ursprüngliche Message -
> Von: Zeev Suraski
> An: hakre
> CC: internals@lists.php.net
> Gesendet: 17:47 Mittwoch, 30.Januar 2013
> Betreff: RE: [PHP-DEV] [RFC] Integrating Zend Optimizer+ into the PHP
> distribution
>
>> > * In that RFC you write:
>
n, a workaround is to provide your own subclass of SplFileObject that
overwrites `__toString()` again. Maybe this is something useful for projects
that make use of the SplFileObject already.
-- hakre
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
- Ursprüngliche Message -
> Von: Lester Caine
> An: "internals@lists.php.net"
> CC:
> Gesendet: 13:42 Dienstag, 5.Februar 2013
> Betreff: Re: [PHP-DEV] Proposal for serious BC compatibility aka language
> versioning
>
> hakre wrote:
>>>
dow of three years to switch between
one PHP version to the other. Additionally if even this time-frame does not
work out for more than *one* version change, you can even skip up to two major
versions to keep up with the
rest of the gang to latest. I think it was never that easy as it is today.
-- hakre
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
.
Would this mean that changing it in PHP 5.5 (or 5.6) would not be an option
because of the rules of backwards compatibility?
>
>I'd try to avoid this casting magic and stick with ->current() if you actually
>mean it.
So do I. I mean, I often foreach anyway.
-- hakre
--
PHP
- Weitergeleitete Message -
> Von: hakre
> An: Zeev Suraski
> CC:
> Gesendet: 17:09 Mittwoch, 30.Januar 2013
> Betreff: Re: [PHP-DEV] [RFC] Integrating Zend Optimizer+ into the PHP
> distribution
>
> - Ursprüngliche Message -
>
>> Von
sing it not only the original author so I ask in internals
first. Just for clarification.
-- hakre
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
Can somebody shed some light why:
http://www.php.net/unsub.php
and if anybody knows, please share. I can
not find much reference to this string. lxr has nothing, even google is sparse.
-- hakre
aving casting list list() can be handy then.
Is this hard to add to core PHP?
-- hakre
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
now I can not
imagine why rewind would be called (apart from using in foreach() for the first
time which implies a rewind and that one is already like I suggest.)
My 2 cents.
-- hakre
- Ursprüngliche Message -
> Von: Nikita Popov
> An: Brian Moon
> CC: PHP internals
&
> Also, currently yield looks very similar to return and I think this is
> a nice thing as it is similar semantically. yield($foo) would give it
> different semantics, imho.
I love this point a lot. Return is very common and yield is some kind of return.
--
PHP Internals - PHP Runtime Developm
~~~
Also it is probably worth to outline on that page that releases are
not supported for historical reasons and that in the future the
duration of support is as outline as in the RFC.
Also the page could have a prominent last updated timestamp as it
contains information
this can benefit from some
clarification, too.
Thank you for your ongoing support
-- hakre
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
a first draft is:
http://i.stack.imgur.com/HYKZm.png
which in turn made me asking questions here for the parts that were not clear
to me.
-- hakre
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
here a date? According to the new release
process it is already EOL because it's over three years now, however the RFC
vote was in that lifetime so I assume that probably there is some transistion
phase. If so, is there a planned date? Any thoughts/plans about PHP 5.3 EOL?
Cheers
-- hakre
20 matches
Mail list logo
