|
Mark Edgar wrote: [...]
However, I feel that in order for such an API to be useful, it must integrate strongly with the core libraries. The "ex" API currently integrates with the core libraries in the following ways:Augmenting the io namespace (io.pipe) Augmenting the os namespace (many functions) Augmenting the file metatable with lock() and unlock() methods Reimplementing os.getenv() Redefining os.remove() to remove directories Returning actual file objects from io.pipe()
could the "ex" (or whatever) library have a parameter to "require" to control whether it loads into "ex" and/or updates io,os etc ? Adrian