On Wed, Apr 29, 2015 at 12:37 AM, Adam Harvey wrote:
> So, please, show respect for the people working hard on PHP 7.0 [...]
Whoa, the "show respect for the people that work" card already ?
Let's all chill. Here are some kitteh.
http://lol.cat/3z
> by not trying to push something in against our
On Apr 29, 2015 5:38 AM, "Adam Harvey" wrote:
>
> On 28 April 2015 at 15:10, Patrick ALLAERT wrote:
> > Le mar. 28 avr. 2015 à 20:42, Kalle Sommer Nielsen a
écrit :
> >
> >> I should probably have been faster at replying, but for PHP7 this is a
> >> no-go. I realize this is a pure internal chang
On Tue, Apr 28, 2015 at 6:00 PM, Stanislav Malyshev
wrote:
> Hi!
>
> > External data can have any form of numbers.
> > Current PHP can handle them as "string". However PHP7's type hint cannot
> > handle numeric data well because it only has "int" and "float" hints.
>
> This is exactly what's wron
Hi!
> External data can have any form of numbers.
> Current PHP can handle them as "string". However PHP7's type hint cannot
> handle numeric data well because it only has "int" and "float" hints.
This is exactly what's wrong with strict typing in PHP. However, if you
use real numeric string and
Hi all,
External data can have any form of numbers.
Current PHP can handle them as "string". However PHP7's type hint cannot
handle numeric data well because it only has "int" and "float" hints.
http://3v4l.org/6J0bZ
There are cases that programmer want/need to handle any numeric values.
e.g. JS
On 28 April 2015 at 15:10, Patrick ALLAERT wrote:
> Le mar. 28 avr. 2015 à 20:42, Kalle Sommer Nielsen a écrit :
>
>> I should probably have been faster at replying, but for PHP7 this is a
>> no-go. I realize this is a pure internal change and have nothing to do
>> with userland, but as currently
Le mar. 28 avr. 2015 à 20:42, Kalle Sommer Nielsen a écrit :
> I should probably have been faster at replying, but for PHP7 this is a
> no-go. I realize this is a pure internal change and have nothing to do
> with userland, but as currently is, we are in feature freeze and it
> creates a bad prec
Hi Dennis,
Le mar. 28 avr. 2015 à 18:33, Dennis Birkholz a
écrit :
>
> just to satisfy my personal curiosity: how can this RFC target 7.0 which
> had the feature freeze over a month ago? Should it not be 7.1 just to
> treat all contributors equal?
>
We are fully aware of the feature freeze and h
On Tue, Apr 28, 2015 at 8:41 PM, Kalle Sommer Nielsen wrote:
> I should probably have been faster at replying, but for PHP7 this is a
> no-go. I realize this is a pure internal change and have nothing to do
> with userland, but as currently is, we are in feature freeze and it
> creates a bad prece
> De : morrison.l...@gmail.com [mailto:morrison.l...@gmail.com] De la part
> > 1. I proposed making class names case-sensitive and it was clearly rejected,
> most considering it is a *huge* BC break for almost no benefit. I personally
> don't know any software which uses class names in a case-insen
Hi Olivier
2015-04-28 15:24 GMT+02:00 Olivier Garcia :
> Dear Internals,
>
> The "Improved Error Callback Mechanism" RFC is now in voting phase.
I should probably have been faster at replying, but for PHP7 this is a
no-go. I realize this is a pure internal change and have nothing to do
with userl
On Tue, Apr 28, 2015 at 8:13 AM, François Laupretre wrote:
>> De : Dennis Birkholz [mailto:den...@birkholz.biz]
>>
>> I would like PHP to make all class/trait/interface names case-sensitive
>> and use only lower-case names for the scalar type hints (same for
>> object, array, etc.). This would sol
Hi all,
Am 28.04.2015 um 15:24 schrieb Olivier Garcia:
> The "Improved Error Callback Mechanism" RFC is now in voting phase.
just to satisfy my personal curiosity: how can this RFC target 7.0 which
had the feature freeze over a month ago? Should it not be 7.1 just to
treat all contributors equal?
I do know about Lithium, but honestly Nate I don't agree with your
complain. While I do understand the frustration of having to update
code because of changes in the underlying platform (PHP7 in this
case), I believe this is a change for the better, and to which
dependent code should adapt.
You ha
> De : Dennis Birkholz [mailto:den...@birkholz.biz]
>
> I would like PHP to make all class/trait/interface names case-sensitive
> and use only lower-case names for the scalar type hints (same for
> object, array, etc.). This would solve most problems. Class names are
> kind of case sensitive in ap
François Laupretre wrote on 28/04/2015 14:35:
I am especially interested by the opinion of Drupal, Wordpress, and other
framework developers. Are there any out there ? Please comment.
If you look in the rest of the thread, you'll see a few:
- Drupal's String class was part of Drupal 8, which
fwiw, the default has just been changed on the "official" php docker
image : https://github.com/docker-library/php/pull/93
I still think it should be the default so that it would just work for
any heroku like hosting or user made php docker containers
knowing that it's the default behavior wi
> De : Rowan Collins [mailto:rowan.coll...@gmail.com]
>
> This part is likely to be rather tricky to implement. How do you know if
> a 'String' class is defined or not?
>
> The Engine would have to do something like this:
>
> - check in-scope use statements for resolutions of 'String' to a
> qua
Dear Internals,
The "Improved Error Callback Mechanism" RFC is now in voting phase.
You can cast your vote on the Wiki [1] and the according patch is
available as a Pull Request [2].
Vote will be open for two weeks, counting from today.
Kind regards,
[1] https://wiki.php.net/rfc/improved_erro
Hi François,
Am 28.04.2015 um 13:32 schrieb François Laupretre:
> - In 7.0, introduce the 'object' (accepts any object instance) and
> 'object(ClassName)' (similar to the bare 'ClassName') type hint syntaxes.
I find this variant extremely nonintuitive and it conflicts with the
behavior of every
On Tue, 2015-04-28 at 13:07 +0100, Rowan Collins wrote:
> François Laupretre wrote on 28/04/2015 12:32:
> > Bare class names are still recognized and priority is given to class names
> > (if a 'String' class is defined, every 'String' or even 'string' type hints
> > will always refer to it).
>
>
François Laupretre wrote on 28/04/2015 12:32:
Bare class names are still recognized and priority is given to class names (if
a 'String' class is defined, every 'String' or even 'string' type hints will
always refer to it).
This part is likely to be rather tricky to implement. How do you know
Hi,
> De : Stanislav Malyshev [mailto:smalys...@gmail.com]
>
> There was a lot of discussion about this topic. Right now, unless
> there's a proposal to fix it that works, I don't see what can be done
> about it.
I wrote a long message some months ago to explain why reserving names was,
IMHO, th
On 28 April 2015 03:50:07 GMT+01:00, Larry Garfield
wrote:
>On 04/27/2015 06:06 PM, Rowan Collins wrote:
>> On 26 April 2015 20:36:12 GMT+01:00, Nate Abele
> wrote:
>> Lithium, CakePHP, and Drupal all have String classes.
>>
>> I gather that Drupal's String class was actually a rather badly
>desi
Am 13.04.2015 um 15:37 schrieb Johannes Ott:
> Hi,
>
> finally I managed to do my first RFC draft.
>
> https://wiki.php.net/rfc/static_class_constructor
>
> I hope I have done everything correct so far and I'm looking forward to
> your feedback on it.
>
> As I already mentioned in the prediscus
> This last is the only one that seems to be a bug to me; I think if you
> step through the others you'll see why they are fine. Maybe the last
> isn't a bug either; I'll try to think about this more but it does
> appear to be a bug.
FWIW, an example that makes the second situation slightly more c
26 matches
Mail list logo
