Re: Fwd: What's up with Quercus?

From: Date: Sun, 29 May 2011 06:24:24 +0000
Subject: Re: Fwd: What's up with Quercus?
References: 1 2 3 4 5 6  Groups: php.internals 
Request: Send a blank email to internals+get-52534@lists.php.net to get a copy of this message
Hi!
- I immediately had to write an extension to give me access to several missing APIs (clock_gettime() and a number of ncurses functions not implemented in the ncurses extension).
So the problem with PHP is that it doesn't include support for any possible API out of the box. While all other languages out there of course do ;)
types not in the original API was just a bonus.) - In general, I have to tiptoe all over everything to avoid getting useless notices/warnings for expected error conditions (such as SIGPIPE on
This is indeed a serious complaint, PHP tends to be over-verbose and errors are expensive. So far there's no BC-compliant way to fix it has been found. I know, I tried at least 3 times :) We need ideas there.
- No threading support.
Threading in PHP wouldn't work. At least the one like they have in Java. Unless you want to mess with thread synchronization, deadlock resolution and other stuff, which 99.9999% of PHP users don't.
No preprocessor. define() makes up for only some of it, closures make up for some more, but still not enough. There are no mature
Here it may be interesting to note so does pretty much any other language except for C.
And yes, it does mean an engine rewrite.
That would be too easy. It also means throwing out most of the existing code and rewriting everything that was done in last 10+ years in PHP. Then the question would be - why do it with PHP? If you designing a language from scratch anyway, there are so many opportunities to explore... -- Stanislav Malyshev, Software Architect SugarCRM: http://www.sugarcrm.com/ (408)454-6900 ext. 227

« previous php.internals (#52534) next »