On Wed, Jun 2, 2010 at 1:37 PM, Michael Wallner wrote:
>
> Now the script:
> ini_set("memory_limit", "2G");
>
> function mib($b) {
>return $b ? number_format($b/1024/1204, 1, ".", "'") : "?";
>
typo: shouldn't this be $b/1024/1024?
John
JFYI & SCNR,
I produced some synthetic numbers of the performance comparing the
new output control layer with the old one -- actually because I
expected the new code to be less efficient than the one we had.
I didn't have the chance to do this until now, because comparing
php-unicode with php-5.
On 01/06/10 14:59, Guillaume F wrote:
Fix bugs i'm fed up to cope with while developping in PHP.
Mr. Miyagi?! Give this man an SVN account *right now*!!
--
Mark Skilbeck
mahcuz.com | gtk.php.net | pecl.php.net/cairo | docs.php.net
--
PHP Internals - PHP Runtime Development Mailing List
To uns
On 01/06/10 14:59, Guillaume F wrote:
Fix bugs i'm fed up to cope with while developping in PHP.
Mr. Miyagi?! Give this man an SVN account *right now*!!
--
Mark Skilbeck
mahcuz.com | gtk.php.net | pecl.php.net/cairo | docs.php.net
--
PHP Internals - PHP Runtime Development Mailing List
To uns
Hi!
2010/6/2 Stas Malyshev
> Hi!
>
>
> Is there some other reason / use case for wanting exceptions? So, I
>> mean, where is the use case where '123abc' will be passed to a
>> type-hinted field where you could catch the exception and do something
>> meaningful to carry on with the execution of t
On Wed, Jun 2, 2010 at 12:49 AM, Chad Fulton wrote:
> Hello!
>
> > As I mentioned, I think that we have to inform the caller about the
> problem
> > (be either a type or a conversion mismatch), so the only options to
> trigger
> > an error, or throw an exception.
> > I like the exception idea bet
