Rasmus Lerdorf wrote:
I think the only valid point for putting this in core is that it does feel more like a core feature than a pecl add-on. However, a number of us are uncomfortable with the impact of it and would like to understand better how people other than yourself would use it, or more likely, mis-use it.
I think this is were I am sitting at the moment ... If a script needs to tidy up memory because something has gone wrong, then in my book the script is faulty? The example of why it is needed does not make sense to me, probably because I don't understand it, firing an action on the database end and trying to then simply tidy up the the php end cache without a clean reload just seems wrong? How do you know what the stored procedure/trigger/business logic has done to the underlying data? But I've never used MySQL :)
-- Lester Caine - G8HFL ----------------------------- Contact - http://lsces.co.uk/wiki/?page=contact L.S.Caine Electronic Services - http://lsces.co.uk EnquirySolve - http://enquirysolve.com/ Model Engineers Digital Workshop - http://medw.co.uk// Firebird - http://www.firebirdsql.org/index.php -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
