Hi! > I don't know if I will be implementing that ext myself. In any case, before > that can happen I will have to create another RFC for converting parse > errors into exceptions and making sure we don't leak memory on failed parse
If we're talking the plunge of putting exceptions into the core engine, wouldn't it make sense to convert most of the fatal errors (especially the "catchable" ones) to exceptions too? Most of them (except for out of memory, timeouts and such) don't really require the engine to shut down, as it seems... So if we're already saying people will have to deal with exceptions in PHP engine anyway, maybe we could make it so that we could have unified handling of them? -- Stanislav Malyshev, Software Architect SugarCRM: http://www.sugarcrm.com/ -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
