Hey Marcus,

What standard stuff? I remember SPL being used as a way to bring features to users which were decided not to have as standards :) Anyway, we won't get back into it as we've talked about it already in person. But anyway, if we decide to have InvalidArgumentException as a standard (which was not the case for most of SPL), then it definitely will make sense to move it to the Engine as the engine will need to know it. Features which make sense to remain as an SPL extension should be treated like a PHP extension.

"non-standard" stuff shouldn't be prefixed to make me personally happy. I think it should be prefixed to make everyone happy, follow coding standards and follow the same rules as everyone.

Andi

At 11:43 PM 8/8/2005 +0200, Marcus Boerger wrote:
Hello Andi,

Monday, August 8, 2005, 11:33:16 PM, you wrote:

> Hi all,

> Finally caught up with this thread.
> I can live with an exception being thrown for a type hint. I think calling
> it InvalidArgumentException would make sense, and the fact that Marcus
> "stole" :) that name for SPL and didn't prefix the name isn't a reason for
> us not to do the right thing... As it would be an engine exception, we'd
> move it to the Engine. This is a good reason why extensions such as SPL
> should prefix their functionality.

SPL delivers those standard stuff not delivered by the engine so it makes no
sense to prefix them with an SPL prefix. Non standrd stuff will have SPL
prefix in future though just to make you happy. Having said that i think
that extension tree belongs either in the engine or stays in the extension
and we go with pure Exception. Remember the reason i out this into SPL in
the first place was to be able to drop all that fancy O stuff. In that sense
i also asked to move reflection api into its own extension, that way adding
another possibility to drop memory space of the excecutable, increasing exe
load time and thereby increasing speed of such special builds.

Best regards,
 Marcus

--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php

Reply via email to