Jim Fulton wrote: > The original use case for CObjects was to export an API from a module, > in which case, you'd be importing the API from the module. The presence > in the module indicates the type. Sure, but it can't hurt to have an additional sanity check. Also, there are wider uses for CObjects than this. I see it as a quick way of creating a wrapper when you don't want to go to the trouble of a full-blown extension type. A small amount of metadata would make CObjects much more useful. -- Greg
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4