Hi Zeev,
As the person who initially proposed and implemented strict_types, I
think this is heading in the wrong direction. Perhaps that directive was
a mistake, if it will lead to so many attempts inspired by it to
fragment the language, including this one. Personally, I don't actually
want
[List etiquette question: is it good form here to change the subject line
when starting a tangential discussion?]
On Sat, 10 Aug 2019 at 00:08, Larry Garfield wrote:
> PHP doesn't have a coherent philosophy. It is proudly directionless,
> steered by whoever happens to be writing code this week.
Hi,
Lack of type information for internal functions in Reflection is a
long-standing issue. In PHP 8 we finally have all the necessary technical
groundwork done to support argument and return type annotations on internal
functions at scale.
The only thing left is to actually add those type annota
I'm happy to help.
Am I correct in thinking that the best way to locate outstanding ones is to
to search for any instances of *ZEND_BEGIN_ARG_INFO* or
*ZEND_BEGIN_ARG_INFO_EX*
in *.c files?
As once they've been converted they'll only appear in stub and header files?
> On 10 Aug 2019, at 17:56, Nikita Popov wrote:
>
> Hi,
>
> Lack of type information for internal functions in Reflection is a
> long-standing issue. In PHP 8 we finally have all the necessary technical
> groundwork done to support argument and return type annotations on internal
> functions a
Hi,
Sorry if I’m missing something, but can’t the process be automated?
i.e. parse the C source files with a script to generate the stubs? If correctly
done, this could be much less error-prone than manual handling.
Benjamin
> Le 10 août 2019 à 14:00, Stephen Reay a écrit :
>
--
PHP Intern
On Sat, Aug 10, 2019 at 2:00 PM Stephen Reay
wrote:
>
> > On 10 Aug 2019, at 17:56, Nikita Popov wrote:
> >
> > Hi,
> >
> > Lack of type information for internal functions in Reflection is a
> > long-standing issue. In PHP 8 we finally have all the necessary technical
> > groundwork done to supp
On Sat, Aug 10, 2019 at 5:37 AM Andrea Faulds wrote:
> As the person who initially proposed and implemented strict_types, I
> think this is heading in the wrong direction. Perhaps that directive was
> a mistake, if it will lead to so many attempts inspired by it to
> fragment the language, includ
Hi all,
I tried as much as I could to stay away from this discussion. My
personal take is that breaking the language in two is a *really bad
idea* (shouldn't I have put caps here instead?).
Anyway, people are commenting a lot on features that adds a feature to
the language, but nothing was being s
On 10/08/2019 11:56, Nikita Popov wrote:
Hi,
Lack of type information for internal functions in Reflection is a
long-standing issue. In PHP 8 we finally have all the necessary technical
groundwork done to support argument and return type annotations on internal
functions at scale.
Question - I
Am 10.08.2019 um 17:04 schrieb Rasmus Lerdorf :
> On Sat, Aug 10, 2019 at 5:37 AM Andrea Faulds wrote:
>
>> As the person who initially proposed and implemented strict_types, I
>> think this is heading in the wrong direction. Perhaps that directive was
>> a mistake, if it will lead to so many att
On 10.08.2019 at 17:54, Mark Randall wrote:
> On 10/08/2019 11:56, Nikita Popov wrote:
>
>> Lack of type information for internal functions in Reflection is a
>> long-standing issue. In PHP 8 we finally have all the necessary technical
>> groundwork done to support argument and return type annotat
On 10/08/2019 17:08, Christian Schneider wrote:
There is a very vocal minority right now asking for BC breaking language
changes who IMHO are a bit too quick dismissing opinions of very distinguished
PHP developers.
I would just question the assertion that it's a vocal minority when
viewed i
On Sat, Aug 10, 2019 at 12:56 PM Nikita Popov wrote:
> Hi,
>
> Lack of type information for internal functions in Reflection is a
> long-standing issue. In PHP 8 we finally have all the necessary technical
> groundwork done to support argument and return type annotations on internal
> functions a
Hi!
> Finally, Zeev, you mention the "PHP philosophy" of being a dynamic
> language. While that may well be your philosophy, and you have every
> right to have it, that has not been the "PHP philosophy" for years,
> as seen by all of the type "stuff" that's been successfully added to
> the langua
Hi!
> I started for the same reason: to help the community pull together and
> argue less, by having a codified set of values.
The risk here however is for the document to be seen as a means to
"argue less" by way of excluding certain points of view from discussion.
That would not be a good thing
On 10/08/2019 11:56, Nikita Popov wrote:
Lack of type information for internal functions in Reflection is a
long-standing issue. In PHP 8 we finally have all the necessary technical
groundwork done to support argument and return type annotations on internal
functions at scale.
Well I tried to p
I must admit that the first time I read Zeev’s email I got anxious... but it is
frustrating that PHP has a WAY better runtime than Python and most other
dynamic languages yet is falling out of fashion. It’s strange given how much
better it actually runs (really being unbiased here). One reason i
18 matches
Mail list logo
