My situation is parsing a number of XML-reports. If parsing goes wrong in any way (XML parsing fails, XML validation fails, database insertion fails), I want to throw an exception. There's a script that batch-processes these files. I want to collect exceptions and give that feedback to the user. I wouldn't consider this bad practice myself (but of course, I'm not very objective in this situation).
Even if I'm wrong about that, I'm not the only PHP-user and it's my humble opinion that the engine should be solid enough to deal with this. Ron "Derick Rethans" <[EMAIL PROTECTED]> schreef in bericht news:[EMAIL PROTECTED] > On Wed, 10 Aug 2005, Ron Korving wrote: > > > Perhaps it would require an revised garbage collection mechanism? If that's > > the case and you think it's worth investing time in, I think it would be > > something for the next major version (6). > > I think it would be better not to abuse Exceptions like this. They are > for exceptional states, which should result in a graceful shutdown of > your application. In that case 'leaking' the memory to the end of the > request isn't a real problem anyway. > > Derick -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
