On Tue, Mar 01, 2005 at 08:55:40PM +0100, Matthieu Moy wrote: > Restricting the list of available functions is dangerous > because it's hard to know if a function call will not call another > function that will itself trigger a hook which itself will call a > forbidden function or something like this.
It becomes a bit easier if we only allow in a given context "pure" functions that do not (seem to) modify program state. Of course it's not foolproof, but much easier than trying to find exactly the functions that are safe to call. -- Tuomo
