es are
*invalid* as class names.
Should we throw fatal errors for functions starting with 2 underscores too?
>
> Regards
>
> François
>
>
> --
> PHP Internals - PHP Runtime Development Mailing List
> To unsubscribe, visit: http://www.php.net/unsub.php
>
Cheers,
Florian Margaine
Hi Zeev,
Le 30 mars 2015 16:17, "Zeev Suraski" a écrit :
>
> All,
>
>
>
> One thing that I think we should change is how we refer to the ‘weak’ type
> hints. The word ‘weak’ has a negative ring to it, and considering this is
> how the language behaves across the board it’s a pretty bad name for
up - but please,
> please fix this - it's a very long standing annoyance.
Cheers,
--
Florian Margaine
signature.asc
Description: PGP signature
orward to me instead of asking the same
questions
> > (in various form but it ends to the same answer).
> >
> > And the patch should be applied sooner rather than later. So we can fix
bugs
> > if there are actual ones in the current implementation.
>
> Hello,
>
> if I had time to set up the compilation of PHP on Windows, I'd do it -
> but I don't. I wanted to try it myself via http://3v4l.org/, but it
> unfortunately doesn't support multiple files.
You can emulate multiple files support by using eval().
>
> Regards
> Pavel Kouril
>
> --
> PHP Internals - PHP Runtime Development Mailing List
> To unsubscribe, visit: http://www.php.net/unsub.php
>
Cheers,
Florian Margaine
a tweak on an earlier version:
> https://wiki.php.net/rfc/voting#discussion_period
I guess that since there was a lot of discussion, shortening to one week
makes sense.
>
> cheers,
> Derick
Cheers,
--
Florian Margaine
signature.asc
Description: PGP signature
s is
sucks.
> > >
> > > On the bright side, anything chosen could always be aliased at the
top of
> > > the file:
> > >
> > > use function __u as u;
> > >
> > > This also sucks, but it sucks a little bit less because the
collisions are
> > > avoided - or at least, avoided in such a way that the onus is on the
user -
> > > and one can still have the sane name.
> > >
> > > First-class support at the syntax level (presumably $foo = u"unicode
> > > string" since we already have $foo = b"binary string") would IMO be
better
> > > and (hopefully?) a long-term goal, but I am aware that it is - and
probably
> > > should be - outside the scope of the current proposal.
> > >
> > > [1] https://searchcode.com/?q=function+u+lang%3Aphp
> > > [2]
> > >
https://github.com/facebook/hhvm/blob/master/hphp/test/slow/ext_icu/uspoof.php#L13
> > >
> >
>
> --
> http://derickrethans.nl | http://xdebug.org
> Like Xdebug? Consider a donation: http://xdebug.org/donate.php
> twitter: @derickr and @xdebug
> Posted with an email client that doesn't mangle email: alpine
>
> --
> PHP Internals - PHP Runtime Development Mailing List
> To unsubscribe, visit: http://www.php.net/unsub.php
Cheers,
Florian Margaine
official Twitter account.
>
> Regards,
>
> Pascal
Cheers,
--
Florian Margaine
signature.asc
Description: PGP signature
> >> >
> >> > declare(strict_types=1);
> >> > namespace Foo {
> >> > }
> >> > declare(strict_types=0);
> >> > namespace Bar {
> >> > }
> >> >
> >> > 2. inside of the namespace:
> >> > namespace Foo {
> >> > declare(strict_types=1);
> >> > }
> >> > namespace Bar {
> >> > }
> >> >
> >> > The problem with the first is clarity (it's easy to miss a declare
and
> >> > not understand that the mode has changed). We pinned declare to the
> >> > top of the file for clarity. I'm not sure this use-case is worth
> >> > breaking that clarity.
> >> >
> >> > The problem with the second is more subtle. With the current
> >> > parser+compiler, that declare would affect the entire file. It would
> >> > take pretty significant changes and restructuring of the parser to
> >> > effect.
> >> >
> >> > We could drop declare() all together and go with something like a
> >> > namespace modifier:
> >> >
> >> > strict namespace Foo {
> >> > }
> >> > namespace Bar {
> >> > }
> >> >
> >> > But I don't think it's worth it to conflate those two together.
Though
> >> > if we did, the syntax "strict namespace;" would be supported for
> >> > non-namespaced strict code.
> >> >
> >> > So in the end, my conclusion is that while it would be nice to
support
> >> > the "compiled file" use-case fully, it's not worth it from a
technical
> >> > level (the risk and degree of change required doesn't offset the
> >> > benefit of it).
> >> >
> >> > So the proposal will remain unchainged and not support the block
> >> > syntax (or changing the mode mid-file).
> >> >
> >> > Thanks
> >> >
> >> > Anthony
> >>
> >> --
> >> PHP Internals - PHP Runtime Development Mailing List
> >> To unsubscribe, visit: http://www.php.net/unsub.php
> >>
> >>
> >
Cheers,
Florian Margaine
Hi,
Le 20 févr. 2015 14:34, "Ferenc Kovacs" a écrit :
>
>
>
> On Fri, Feb 20, 2015 at 8:54 AM, Florian Margaine
wrote:
>>
>> Hi Ferenc,
>>
>> Ferenc Kovacs writes:
>>
>> > Hello!
>> >
>> > The PHP development
from the changelog:
> Removed support for multi-line headers, as the are deprecated by RFC
> 7230.
Isn't this a BC break?
>
> Ferenc Kovacs & Julien Pauli
Cheers,
--
Florian Margaine
signature.asc
Description: PGP signature
thing more suited for this out there?
Maybe something like this would help?
http://underscorejs.org/docs/underscore.html
>
> -Rasmus
Cheers,
--
Florian Margaine
signature.asc
Description: PGP signature
hether or not
he wants strict typing.
>
> --
> PHP Internals - PHP Runtime Development Mailing List
> To unsubscribe, visit: http://www.php.net/unsub.php
>
Cheers,
Florian Margaine
be under active
> development.
Not under active development doesn't mean that the application shouldn't
be able to upgrade PHP and enjoy the bug/security fixes or performance
improvements that new versions provide.
>
> Best,
> Stelian
>
Cheers,
--
Florian Margaine
signature.asc
Description: PGP signature
Hi,
Le 17 déc. 2014 09:54, "Ferenc Kovacs" a écrit :
>
> Hi,
>
> while readon through
http://www.garfieldtech.com/blog/on-drupals-leadership,
> I've realized that there is a bunch of similarities between php internals
> and drupal (which isn't that surprising), so I thought they guys around
> the
tor who gave up.)
Now, if the reason people want PHP 5.7 is to extend PHP 5 lifetime, then
it's another matter, and the lifetime of existing versions could be
extended.
Just my $0.02.
Cheers,
Florian Margaine
h` method can just `return
spl_object_hash($this);` to have an object id.
> --
> Rowan Collins
> [IMSoP]
>
>
> --
> PHP Internals - PHP Runtime Development Mailing List
> To unsubscribe, visit: http://www.php.net/unsub.php
>
Cheers,
Florian Margaine
Hi,
On Fri, Dec 12, 2014 at 5:35 PM, guilhermebla...@gmail.com <
guilhermebla...@gmail.com> wrote:
>
> RFC is updated exposing both possible usages with both explanations.
> Hope it doesn't confuse even more.
>
>
Perfect! Thanks.
Cheers,
--
Florian Margaine
What is proposed? The example? The
votes? What does `final` has to do with `static`?
I'm confused.
> On Fri, Dec 12, 2014 at 11:18 AM, Florian Margaine
wrote:
>>
>> Hi,
>>
>>
>>
>> On Fri, Dec 12, 2014 at 5:12 PM, guilhermebla...@gmail.com <
gui
ts 2 options. The RFC is in a weird state where it
mentions "abstract final" but doesn't explain anything about them. The
votes don't seem to be what the example is...
Could you edit your RFC?
>
>
> Happy voting!
>
> Regards,
>
> --
> Guilherme Blanco
> MSN: guilhermebla...@hotmail.com
> GTalk: guilhermeblanco
> Toronto - ON/Canada
>
Cheers,
--
Florian Margaine
Hi,
Le 11 déc. 2014 09:08, "Sebastian Bergmann" a écrit :
>
> $ git status
> On branch PHP-5.6
> Your branch is up-to-date with 'origin/PHP-5.6'.
> nothing to commit, working directory clean
>
> $ ./configure --disable-all
> .
> .
> .
> Thank you for using PHP.
>
> config.status: error:
f possible :)
Regards,
--
Florian Margaine
Hi Joe,
On Mon, Nov 17, 2014 at 8:42 AM, Joe Watkins wrote:
> On Sat, 2014-11-15 at 11:16 +0100, Florian Margaine wrote:
> > Hi list,
> >
> > As of today, most of the SAPIs have a lot of code duplication with
> > regards to HTTP headers parsing/handling.
>
;d like to avoid that.
Should I create a `sapi/main/` folder for common functions across the
SAPIs? Or should each SAPI remain completely independent from each
other, even if it means duplicating code?
Regards,
--
Florian Margaine
- major BC break: major versions only. 5 major BC breaks allowed per major
version.
- minor BC break:
- minor versions: 5 minor BC breaks allowed.
- patch versions: 1 BC break allowed.
Thoughts? Am I thinking too much? Is this idea unfeasible? Is it a good
idea?
Regards,
--
Florian Margaine
---
> Contact - http://lsces.co.uk/wiki/?page=contact
> L.S.Caine Electronic Services - http://lsces.co.uk
> EnquirySolve - http://enquirysolve.com/
> Model Engineers Digital Workshop - http://medw.co.uk
> Rainbow Digital Media - http://rainbowdigitalmedia.co.uk
>
> --
> PHP Internals - PHP Runtime Development Mailing List
> To unsubscribe, visit: http://www.php.net/unsub.php
>
>
Regards,
--
Florian Margaine
Hi,
On Tue, Nov 4, 2014 at 2:28 PM, Lester Caine wrote:
> On 04/11/14 13:13, Florian Margaine wrote:
> > On the basis of 'If it's not broken', what is actually broken, and
> what
> > is just a matter of 'I don't like that way of working'
.Caine Electronic Services - http://lsces.co.uk
> EnquirySolve - http://enquirysolve.com/
> Model Engineers Digital Workshop - http://medw.co.uk
> Rainbow Digital Media - http://rainbowdigitalmedia.co.uk
>
> --
> PHP Internals - PHP Runtime Development Mailing List
> To unsubscribe, visit: http://www.php.net/unsub.php
>
>
Regards,
--
Florian Margaine
's
> scope should be.
>
> Joe, if I got this wrong, then please say so :-)
>
> cheers,
> Derick
>
>
> --
> http://derickrethans.nl | http://xdebug.org
> Like Xdebug? Consider a donation: http://xdebug.org/donate.php
> twitter: @derickr and @xdebug
> Posted with an email client that doesn't mangle email: alpine
>
> --
> PHP Internals - PHP Runtime Development Mailing List
> To unsubscribe, visit: http://www.php.net/unsub.php
>
>
--
Florian Margaine
and to do it would be a bit of an arbitrary restriction.
> > maybe we could do something like introducing a new $overwrite = true
> option
> > to the function signature, but setcookie already has 7 arguments, so
> > probably isn't a great idea.
>
> --
> > Ferenc Kovács
> > @Tyr43l - http://tyrael.hu
>
Regards,
--
Florian Margaine
implementation detail as of now. There could certainly be other/better
ways
> to accomplish this. I just want to keep it as simple as possible for now
> without introducing more configuration nightmares that people often
> complain about. I really don't like the idea of adding yet another INI
> directive to control this behavior (making it harder to port).
>
> What do you propose?
Regards,
Florian Margaine
t; what others think or how they feel we might approach this problem more
> cleanly.
>
> Thanks,
> Sherif
>
The other thing I don't like in your RFC is the removal of superglobals.
Sure, they're not the best interface out there, but breaking *every single*
codebase out there is not the way to go. Especially if we don't want a
perl6/python3-like failure to adoption.
Regards,
--
Florian Margaine
g it a bit too far?
>
I think Rasmus made it clear what the original naming meant: it were form
methods, not related at all to HTTP methods.
>
> --
> Stanislav Malyshev, Software Architect
> SugarCRM: http://www.sugarcrm.com/
>
> --
> PHP Internals - PHP Runtime Deve
in Williams
> Linux/GNU Consultant - Mail systems, Web sites, Networking, Programmer, IT
> Lecturer.
> +44 (0) 787 668 0256 http://www.phcomp.co.uk/
> Parliament Hill Computers Ltd. Registration Information:
> http://www.phcomp.co.uk/contact.php
> #include
>
> --
> PHP Internals - PHP Runtime Development Mailing List
> To unsubscribe, visit: http://www.php.net/unsub.php
>
>
Regards,
--
Florian Margaine
her magic underscore method that's called when an object
> is about to be put into an array as a key (or similar situations)
>
> Philip
>
>
> --
> Sensational AG
> Giesshübelstrasse 62c, Postfach 1966, 8021 Zürich
> Tel. +41 43 544 09 60, Mobile +41 79 341 01 99
> i...@sensational.ch, http://www.sensational.ch
>
--
Florian Margaine
Erratum: all the request_* functions except request_get() take the request
object/array as 1st argument.
Le 14 oct. 2014 18:21, "Florian Margaine" a écrit :
>
> Hi,
>
> If it were me, I'd rather delete all the superglobals. It's a horrible
API, I don't thin
HP folks, I’m fairly confident
> > someone would make the association that either $_GET or $_POST is bound
> > strictly to the HTTP verb of the same name. Adding aliases gives these
> > vars a more semantic name while not causing a massive BC breakage.
>
> I think 20+ years of history has proven this to be a non-issue. Of all
> the things that people get confused by in PHP, $_GET/$_POST are right
> near the bottom of the list.
>
> -Rasmus
>
>
>
> --
> PHP Internals - PHP Runtime Development Mailing List
> To unsubscribe, visit: http://www.php.net/unsub.php
>
>
--
Florian Margaine
Hi!
How is it better than:
$idx3 = $_POST['idx1']['idx2']['idx3'];
?
Regards,
Florian Margaine
Le 7 oct. 2014 18:05, "Mathias Grimm" a écrit :
> Hi,
> I would like to suggest something for php like a class I am using
>
> https://github.co
ssary trust to
give, when we can simply not have the file?
>
> --
> Stanislav Malyshev, Software Architect
> SugarCRM: http://www.sugarcrm.com/
>
--
Florian Margaine
the file every time ensures there is no hidden
bug.
Just my 2 cents.
Regards,
Florian Margaine
Le 2 oct. 2014 21:04, "Stas Malyshev" a écrit :
> Hi!
>
> > Case in point: The current zend_language_scanner.c has been generated by
> > Andrea, who uses a different re2c ve
I see, thanks for the answer!
On Fri, Sep 26, 2014 at 1:43 PM, Ferenc Kovacs wrote:
>
>
> On Fri, Sep 26, 2014 at 1:29 PM, Florian Margaine
> wrote:
>
>> Hi internals,
>>
>> The question is in the title :-)
>>
>> As far as I know, most projects fol
fix/feature up to the new branches (first
PHP-5.6, then master).
Is there a convention for php-src? Or is it "whatever the dev wants"?
--
Regards,
*Florian Margaine*
Le 25 sept. 2014 12:54, "Pierre Joye" a écrit :
>
> On Thu, Sep 25, 2014 at 12:22 PM, Florian Margaine
wrote:
> > Hi,
> >
> > Joe Watkins wrote (for fun) a new operator, `addressof`. Code is here:
> > https://github.com/krakjoe/php-src/compare/addressof
&g
s_resource().
>
> Is it really necessary? I could imagine a transition with 5.7 for
> that, similar to gmp.
>
> Cheers,
> --
> Pierre
>
> @pierrejoye | http://www.libgd.org
>
--
Regards,
*Florian Margaine*
Hi,
I do believe that the UString class would benefit from such a change.
Why would it be confusing to implement this?
Regards,
*Florian Margaine*
Le 23 sept. 2014 12:42, "Michael Wallner" a écrit :
> On 2014-09-23 11:45, Leigh wrote:
> > On 23 September 2014 10:35, Mic
re as to how it should
be handled.
Regards,
*Florian Margaine*
On Mon, Sep 22, 2014 at 10:05 PM, Levi Morrison wrote:
> On Mon, Sep 22, 2014 at 3:37 PM, Pierre Joye wrote:
>
> > On Sep 22, 2014 3:31 PM, "Derick Rethans" wrote:
> > >
> > > On Mon, 22 Se
Hi,
Having done a few PRs now, I\'d like to assign bugs to myself on
bugs.php.net to avoid having several people working on the same one. For this,
I need a php.net account :-)
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
Hi Derick,
Thanks for your answer!
Indeed, I did plan on doing another PR for 5.6 while keeping ZEND_ARG_INFO.
I'll review your notes and take care of them.
Regards,
*Florian Margaine*
On Mon, Sep 22, 2014 at 1:29 PM, Derick Rethans wrote:
> Hi Florian,
>
> On Sun, 21 Sep
Sounds like a great idea! Don't forget to update
https://bugs.php.net/bug.php?id=68049 when it'll be done.
Regards,
*Florian Margaine*
On Mon, Sep 22, 2014 at 9:20 AM, Kévin Dunglas wrote:
> I've recently proposed a refactoring of FILTER_VALIDATE_URL:
> https://github
Oh, IE. *sigh*
Adding a new flag sounds like a good idea indeed,
`FILTER_VALIDATE_UNCOMPLIANT_URL` sounds good enough?
I guess it should accept underscores and domain names starting with numbers
too.
Regards,
*Florian Margaine*
P.S: sorry Kevin for the double mail.
Le 22 sept. 2014 09:03
::offsetUnset, but I'd like internals' opinion on this.
Regards,
*Florian Margaine*
opinion, using ZEND_ARG_OBJ_INFO means that we're going to the right
direction: fixing the type hints and the reflection of the classes.
The PR could be backported to 5.* by using ZEND_ARG_INFO to avoid BC breaks.
Regards,
*Florian Margaine*
tml/rfc3986#section-3.2.2> be respected, or
should PHP be lenient like browsers and accept more?
Regards,
*Florian Margaine*
()` should noisely fail
Both solutions look fine to me, but I'm not sure what PHP should do. Should
it be resilient and silently fix the situation?
Regards,
*Florian Margaine*
ps://github.com/php/php-src/pull/795/
PHP issue: https://bugs.php.net/bug.php?id=67736
Regards,
*Florian Margaine*
54 matches
Mail list logo
