Currently, the function sql∆∆load_library gets called when the SQL.apl gets executed to load the native library and then gets erased. This is a problem in the following scenario:
1. Create an APL workspace
2. Copy in the SQL library code (this loads the native library)
3. Save your application workspace (that now includes the SQL code)
4. Exit APL
5. Startup APL
6. Load the application you saved (that already includes the SQL code)
At this point you have no easy way of loading the native library.
The fix for this would be to:
A. Do not auto erase sql∆∆load_library
B. Rename sql∆∆load_library to SQL∆LoadLibrary to be consistent with the other SQL function names.
Doing this, an application can call SQL∆LoadLibrary upon startup to be sure it is loaded.
On an unrelated note, SQL.apl includes a do-nothing function named sql∆∆tryload. It should probably be deleted.
Thanks.
Blake