News for hackers. Stuff that matters.
Re:Announcing a specification for PHP by TazeTSchnitzel on Wednesday July 30, 2014 @03:58PM (#8110559)
Nikita proposes methods on primitive types: http://nikic.github.io/2014/03/14/Methods-on-primitive-types...

Myself, I like this proposal.

Re:Announcing a specification for PHP by agumonkey on Wednesday July 30, 2014 @04:36PM (#8110778)
Soon all dynamic languages will be one. Except for the method call syntax.
Re:Announcing a specification for PHP by Shorel on Wednesday July 30, 2014 @05:14PM (#8111017)
Actually, that's Uniform Function Call Syntax http://www.drdobbs.com/cpp/uniform-function-call-syntax/2327...

And it doesn't make a language 'dynamic'. The language I found with UFCS is both static and compiled.

Re:Announcing a specification for PHP by recursive on Thursday July 31, 2014 @12:00AM (#8112396)
Walter notes two advantages of that scheme over extension methods. One of them is that extension methods can not be called with the standard prefix notation. This is not actually true, at least in the languages most known for extension methods, Visual Basic and C#.
Re:Announcing a specification for PHP by agumonkey on Wednesday July 30, 2014 @11:01PM (#8112264)
That's not what I meant. PHP code was built around its SPL, if they accept nikic proposal, people will code using base types with similar operations set found in many dynamic languages.

What's left is [1,2,3]->slice(1,2) versus [1,2,3].slice(1,2)

ps: dynamic can be compiled and compiled can be interpreted, so I understand that it is unrelated.

Re:Announcing a specification for PHP by wisty on Thursday July 31, 2014 @11:12AM (#8114548)
See https://github.com/devyn/unholy (Ruby to Python bytecode, then Python bytecode to Python source). Used to run Ruby on Google App Engine, I think.
Re:Announcing a specification for PHP by dragonwriter on Thursday July 31, 2014 @11:22AM (#8114616)
The usual way to run Ruby on GAE is just to use JRuby on the App Engine Java runtime. Unholy has been dead for years, and from the commit messages seems to have never gotten to more than very basic functionality; I doubt very much that you could run meaningful code with it, on GAE or otherwise.
Re:Announcing a specification for PHP by kenshaw on Wednesday July 30, 2014 @08:35PM (#8111806)
You mean all dynamic languages are Lisp?
Re:Announcing a specification for PHP by agumonkey on Wednesday July 30, 2014 @10:54PM (#8112248)
Having read Lisp in small pieces I can't hide that it was on my mind. But without parens smugness, right now php, python, es6 are getting closer and closer.
Re:Announcing a specification for PHP by korzun on Wednesday July 30, 2014 @10:44PM (#8112207)
I like it too, it's clean. But reality is that PHP will have to be backwards compatible.

Which means you will see old function based implementations and new object based implementations.

Image dealing with both implementations within the same code base? Eek.

Re:Announcing a specification for PHP by gmjosack on Wednesday July 30, 2014 @11:44PM (#8112362)
This was how a lot of perl5 was when I used it in the early 2000s.