Re: Creating and using a .DLL/.SO?
- Posted by mattlewis (admin) Dec 26, 2008
- 1130 views
My basic idea is to create a system where the user can't even tell the difference between using an interpreted vs translated include file.
...
I do not see how this would handle:
open_dll("dbi_mysql.so") open_dll("dbi_pgsql.so") open_dll("dbi_eds.so")
Where all three .so files defined 20 functions/procedures of the exact same name. If the plan is to allow namespaces on these, then that would make life pretty difficult to make transparent calls. For instance, to further the above code, the programmer would have to know what database backend was being used:
mysql:dbi_open() pgsql:dbi_open() eds:dbi_open()
The whole idea of many plugin modules, dbi interfaces, etc... is to make it so the programmer could care less what module/dbi interface was being used.
Yes, this is a separate issue. My short answer would be that the translated version would be handled (from the user's perspective) the same as it would be if your modulized data access layer were interpreted.
Matt
