Re: PHP 4.0 Bug #3779 Updated: Crash in syntax hilighter
| From: | Stanislav Malyshev | Date: | Thu, 09 Mar 2000 13:38:36 +0000 |
| Subject: | Re: PHP 4.0 Bug #3779 Updated: Crash in syntax hilighter | ||
| References: | 1 | Groups: | php.dev |
| Request: | Send a blank email to php-dev+get-16576@lists.php.net to get a copy of this message | ||
FN>> In some cases, I think, it will be faster because you have
FN>> to write equivalent code which has already been done in C++,
FN>> which is much more efficient and short.
Well, I'm far from supposing that anybody did serious effort on
speed-optimizing C++ STL. Or do you have hard facts on that?
FN>> It can greatly reduce the overheads (if any) in hashes,
FN>> maps, arrays etc. since they are just by a number of people
FN>> world-wide, so the standard library for C++ is hyper-efficient!
Again, do you have any hard facts on that? Most of top-used programs in
the world (one of which you probably are using just now) aren't exactly
known as hyper-efficient. They are more known as the opposite, as I heard.
FN>> C++ is support on almost (I don't know which doesn't) all platforms!
FN>>
FN>> the 'new' operator is more efficient than malloc().
How is that, knowing that new operator on most systems I saw *is*
malloc() (or analogous alloc() function) plus something yet?
--
Stanislav Malyshev stas@zend.com
+972-3-6139665