On Fri, Mar 13, 2015 at 8:51 PM, Scott Arciszewski sc...@arciszewski.me wrote:
Pavel_Kouřil wrote:
- It is a setting that changes the language's behavior; I don't
think that it matters whether or not it would be an INI setting or the
declare() one, because both of them are bad.
It allows
On Mar 15, 2015 6:23 AM, Pavel Kouřil pajou...@gmail.com wrote:
On Sun, Mar 15, 2015 at 9:56 AM, Leigh lei...@gmail.com wrote:
On 15 March 2015 at 08:42, Pavel Kouřil pajou...@gmail.com wrote:
Sure, per-file is better than ini setting, but better doesn't mean
good (because it is still
On Sun, Mar 15, 2015 at 4:52 AM, Pavel Kouřil pajou...@gmail.com wrote:
So - are you saying that it would be easy to remove this feature from
the language once people would realize it's register_globals (and any
other settings that change how code behaves) all over again?
Actually, it would
On 15 March 2015 at 08:42, Pavel Kouřil pajou...@gmail.com wrote:
Sure, per-file is better than ini setting, but better doesn't mean
good (because it is still a pretty bad approach). The ini setting at
least has the option to be turned off in code once everyone realizes
it was a bad idea
On Sun, Mar 15, 2015 at 9:56 AM, Leigh lei...@gmail.com wrote:
On 15 March 2015 at 08:42, Pavel Kouřil pajou...@gmail.com wrote:
Sure, per-file is better than ini setting, but better doesn't mean
good (because it is still a pretty bad approach). The ini setting at
least has the option to be
Maciej Sobaczewski in php.internals (Fri, 13 Mar 2015 19:04:30 +0100):
I think (and I do really hope) that some of those 33 votes came from
misunderstanding of the proposal.
Maybe. But on the other hand there are some names in the v0.5 no-camp,
that you would want to be on the yes side in such a
Eli, I don't even try to. However, when the result is tentative, it's
good to be sure that we don't have any incorrect votes.
Yes, I'm in favor of this RFC and I never concealed it, *but* I'm not
going to discredit any of the voting members. If the final decision will
be negative I'll just
On Fri, Mar 13, 2015 at 7:04 PM, Maciej Sobaczewski so...@php.net wrote:
Currently Scalar Type Declarations are going to fall. We have 33 No votes
and I really wonder why there is almost no justification for them. I know
that it's not required, but it is a matter of good taste in whole voting
Currently Scalar Type Declarations are going to fall. We have 33 No
votes and I really wonder why there is almost no justification for them.
I know that it's not required, but it is a matter of good taste in whole
voting proces.
I think (and I do really hope) that some of those 33 votes came
I really don't think that you want us to be going down the
Republican/Democrat Redistricting game Maciej, not during an active
vote at least. Attempting to 'help one side win' by deciding that some
people's votes on the side that you are not for ... should just be
discounted.
Is not the way to
Pavel_Kouřil wrote:
- It is a setting that changes the language's behavior; I don't
think that it matters whether or not it would be an INI setting or the
declare() one, because both of them are bad.
It allows people who want strict typing to declare it on a per-PHP-file
basis. An INI
Thanks for the clear statement, which lights up the fog a little bit for.
Watching out for a scalar typehints feature for round about 10 years
without knowing about this internal list, I always was wondering what
can be so complicated to implement it, because I already evaluated some
different
Thanks Anthony for the thorough explanation and your view on the matter,
highly appreciated. I am sure that long-term developers have gone through
both ends of the strong types, either loving their lack while picking up
php for
the first time, either cursing it's lack later on along the way.
As
13 matches
Mail list logo
