Re: [citations for] Re: [PHP-DEV] Experiments with a threading library for Zend: spawning a new executor
| From: | Stas Malyshev | Date: | Wed, 19 Jan 2011 19:58:36 +0000 |
| Subject: | Re: [citations for] Re: [PHP-DEV] Experiments with a threading library for Zend: spawning a new executor | ||
| References: | 1 2 3 4 5 6 7 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-51326@lists.php.net to get a copy of this message | ||
Hi!
I think the point is that the php language itself does not provide solid construct for writing rock-solid code. Yes, there are many programmers/hackers that can, but the effort they put is huge.I think this is completely untrue.
In Java you are free to extend a class --yours or imported-- without worries about it's internal implementation. Is that possible in PHP? nope. __construct breaks that.Could you please explain what you mean? How __construct breaks extending a class?
IMHO, as a simple PHP programmer, the language should provide the simplest language construct and the engine should handle all the complexity under the hood.I see no way of hiding threads complexity "under the hood" - if you want threads, you'll need to deal with synchronization, locking, race conditions, etc. Do you see any way to avoid it? -- Stanislav Malyshev, Software Architect SugarCRM: http://www.sugarcrm.com/ (408)454-6900 ext. 227