artups using PHP and a pretty nice city.
Until that, could we consider making a poll on the website to let the
users vote for their feature changes and so we can really gauge what
the community that uses PHP wants / needs?
Kind regards
Florin Patan
https://github.com/dlsniper
http://www.linkedin.com/in/florinpatan
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
On Thu, Sep 12, 2013 at 4:46 AM, Rasmus Lerdorf wrote:
> On 09/11/2013 05:34 PM, Florin Patan wrote:
>> - lack of a clear roadmap: as I said earlier, can someone really tell
>> what's in the next two versions of php from now
>
> That's never going to happen. We don
s and people are drove off
sooner or later by it and that's what we should prevent and improve.
@Jordi
Internals mailing lists rules say to break silence when you have
something to say and that's what I've did. Like it or not this is the
truth and if everyone knows it and nobody sa
On Wed, Sep 11, 2013 at 2:35 PM, Johannes Schlüter
wrote:
> On Wed, 2013-09-11 at 12:44 +0200, Florin Patan wrote:
>> - having a RFC to make a language change requires to have a patch
>> which if you don't know C and internals you got no chance of doing.
>
> Well, so
h
> finding answers to technical questions on the web. Well discourse is by on
> of the authors, with the same spirit. It seems like very good software, very
> far from what "forum" comes to everybody's mind, and quite appropriate to
> *some* of the problems here.
&g
re still ahead of others
- I'll just be against everything today as I didn't had enough sugar
in my coffee
attitudes as it's really not productive for developers and companies
that are still using PHP.
Florin Patan
https://github.com/dlsniper
http://www.linkedin.com/in/florinpatan
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
function at runtime.
>
> The methods route is a poor choice. If we use classes at all, separate the
> responsibility of each type of escaping to a separate class. Escaping JSON
> and HTML code have little (possibly nothing) in common and do not belong in
> the same class.
How a
out £ or Ψ?
I'd really like that the last one in PHP 6 if it's not possible in 5.6.
Thanks
Florin Patan
https://github.com/dlsniper
http://www.linkedin.com/in/florinpatan
if I miss one comma?
Named parameters would also solve a problem from another RFC that's
being proposed right now if I understand correctly so why not go for
that?
Kind regards
Florin Patan
https://github.com/dlsniper
http://www.linkedin.com/in/florinpatan
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
n if you don't think it's necessary, there are surely things you
> think can be improved (and hence everyone wins).
>
> Thanks
>
> Anthony
>
>
Those are the idea that I have in regards to this RFC. Hope they help.
Kind regards,
Florin Patan
https://github.com/dlsniper
http://www.linkedin.com/in/florinpatan
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
e and even if I won't use it, as long as it won't affect the
global performance, I can live with it.
Regards,
Florin
Florin Patan
https://github.com/dlsniper
http://www.linkedin.com/in/florinpatan
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
to any other script out there, how will this
change affect the other applications out there?
The way I'd see this would be to include the notion of global
libraries to Composer, with versioning and so on. Then, once people
get used to this concept, move Composer to PHP (not necessarily in C),
On Thu, Jul 11, 2013 at 10:52 PM, Sara Golemon wrote:
> I agree 100%.
>
> This particular item has been in the works since before I joined the team
> and I've given them a bollocking out over it. You may have noticed
> UConverter and a few other changes which WERE proposed to internals@ prior
> t
moving from gist to RFC I'll try and
contact the authors and see if they are still interested in this
topic.
As for the HHVM stuff, lets move to the other thread.
Best regards,
Florin
Florin Patan
https://github.com/dlsniper
http://www.linkedin.com/in/florinpatan
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
On Wed, Jul 10, 2013 at 10:58 AM, Patrick ALLAERT
wrote:
> Hello Florin,
>
> 2013/7/10 Florin Patan :
>> Since you brought up the discussion, would you think it would make
>> more sense to actually start and integrate HHVM into PHP rather that
>> patching it up?
>&g
t; -Sara
>
> P.S. - Your reply only went to me, but I assume you wanted to include
> internals@ so I put them back in the To: line.
Thanks for your input Sara, everything sounds very interesting. In all
fairness I haven't looked at HHVM but I from what you described about
this
ycle there's only so much patching up you can do
before you can't patch it anymore.
Thanks.
Best regards,
Florin
Florin Patan
https://github.com/dlsniper
http://www.linkedin.com/in/florinpatan
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
nality, but what if you have this in your code and
you decide to remove the new keyword 'super' or whatever so that you
can skip that constructor? Could it be that you just broke your whole
app because of this?
Please think of the downsides as well when thinking of new features
like this
Hi,
Could you give some real scenarios for this since you are in such a
position and you also see this metric ton of goodness? I think they
would help understanding the benefits much better and would also help
clear the waters a but.
Can you come up with some bad scenarios for this as well?
Best regards
Florin Patan
https://github.com/dlsniper
http://www.linkedin.com/in/florinpatan
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
out that these issues don't really exist in general
> (they are just a perspective based on an approach, rather than inherent to
> the concept), I'm not sure how... You have a different approach to code than
> I do. That doesn't mean either of us is wrong. It just means
how would the engine then treat this case:
$array = array();
$array['level1.1']['level2']['level3'] = 'value';
$array['level1.2'] = new StdClass();
foreach($array as $level1 as $level2 as $level3) { ... }
Best regards
Florin Patan
https://github.com/dlsniper
http://www.linkedin.com/in/florinpatan
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
n debugging this
and how to eventually fix it?
Also, while I'll fix this I plan to write an article about starting
from scratch and document every step in order to identify where the
bug is located and how to test/fix it so that others could use this
information.
Thanks.
Best regard
elves.
>>
>> While I do recognize that this is somewhat trivial to anyone who knows the
>> proper formula, I feel as though it would serve the PHP community well.
>> Much the same as the pow() or pi() functions do. I appreciate your thoughts
>> on this ma
others it's extremely useful, do you want to
argue that we don't need this because ?
Best regards
Florin Patan
https://github.com/dlsniper
http://www.linkedin.com/in/florinpatan
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
ogrammer as
> shooting himself.
>
> Julien.Pauli
Hi,
Type juggling is explicitly not allowed in the draft and I would hope
it can remain the same in the final implementation.
That's actually one of the things I want to prevent.
I love PHP because of type juggling which can be very
If the feedback will be positive for this, as it is right now, I would
also like to start working on a patch for this in 2-3 weeks maybe so
this is a early request for help for anyone that could point me out in
the right direction or champion this patch. I'll make another request
whe
ing a code review,
when I see that a class implements a certain interface or a parameter
has a certain type-hint then I can be sure that I won't need to review
the interface and the implementation to match all the possible methods
in that class and if I'm using a third party app review that as well
to make sure that the guy who's using this 'weak type-hinting' aka
protocol type hinting as you call it won't mess up.
I understand your idea, but for me, the problem that would generate in
real world scenario where you have junior programmers, trainees,
people that don't test the code before they deploy it (or that don't
write tests at all, like me).
Can you please address these issues?
Regards
Florin Patan
https://github.com/dlsniper
http://www.linkedin.com/in/florinpatan
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
e of his/her time to help me out.
This said, thank you very much for your time, consideration and
feedback on this subject.
Best regards,
Florin
Florin Patan
https://github.com/dlsniper
http://www.linkedin.com/in/florinpatan
--
PHP Internals - PHP Runtime Development Mailing List
To unsu
name suggests, exceptional cases, while a bad
credential for a user login is not :)
I also believe, and I might not be the only one with this, that
exceptions used for flow control is a good sign of bad design.
If you follow this way of thinking, everytime you throw an exception,
you would want to
them.
If I got this wrong then maybe you should consider improving your
examples because right now, from those examples alone it just looks
like a more problematic way of having a object hinted at.
Best regards
Florin Patan
https://github.com/dlsniper
http://www.linkedin.com/in/florinpatan
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
ion)
{
sleep(3);
}
}
And I think the RFC should also add a: Disadvantages section so that
it could help people looking on it and proving that you've done all
the research correctly.
Thanks
Florin Patan
https://github.com/dlsniper
http://www.linkedin.com/in/florinpatan
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
#x27;
optimizations for the first time and mark it as passed once;
- next request, load the compiled version, apply another round of
optimization then mark it as a second pass
- repeat the above step until the optimization passes in the said file
= opcache.passes value
This way only the initial
I want to help out with bug handling (as Rasmus indicated on IRC)
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
33 matches
Mail list logo