RE: Hooks for I/O, memory, etc?

[Pyrogon Public <public@...>]

> The drawback is that everyone using Lua would have to start 
> it with something like
> 
>   lua_open(&realloc);

Compared to using the language as a whole, this seems like a trivial
matter.  Startup and initialization -- especially if it's optional -- is
easy to document, debug and understand.  Patching the core Lua code
isn't =)

Brian