Re: Return Type Hinting for Methods RFC
| From: | Stefan Marr | Date: | Fri, 23 Dec 2011 00:30:09 +0000 |
| Subject: | Re: Return Type Hinting for Methods RFC | ||
| References: | 1 2 3 4 5 6 7 8 9 10 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-57047@lists.php.net to get a copy of this message | ||
Hi:
On 23 Dec 2011, at 01:14, Stas Malyshev wrote:
> BTW, which languages you are talking about? PHP peers - Python, Ruby, Perl, Javascript (to some
> measure), etc. don't have typing as far as I know. Comparing PHP to statically compiled
> strictly typed languages does not seem very useful to me. So could you clarify what do you mean?
Perhaps the newest kid on the block deserves some reference for making optional typing more
mainstream and being more radical about being checkable documentation: http://www.dartlang.org/docs/technical-overview/index.html
Dart's type system is not sound, and the design goal is to never (NEVER) interfere with
execution semantics. It is more radical than previous research systems with its not-sound approach
of making generics understandable, but people seem to appreciate that in practice.
It might give the necessary example to bridge the worlds between the 'PHP should be more like
Java' and the 'PHP should be more like PHP' people.
Best regards
Stefan
--
Stefan Marr
Software Languages Lab
Vrije Universiteit Brussel
Pleinlaan 2 / B-1050 Brussels / Belgium
http://soft.vub.ac.be/~smarr
Phone: +32 2 629 2974
Fax: +32 2 629 3525