Using native euphoria in edbi
- Posted by jimcbrown (admin) Oct 15, 2009
- 1224 views
Forked from Re: eDBI is born, feedback wanted
Ok, so for the time being I've modified edbi.e to allow one to specify either a dll or a set of routine ids. So now I can just include edbi_eusql.e directly in example_2.ex, and create a list of routine ids, and it just works.
Is there a reason why this is disallowed? I understand that making and using a DLL is faster and more portable (drivers can be written in pure C), but the hassles of having to though translation each time to debug the library is a ... well, a hassle.
When writing a edbi driver in euphoria, it's a lot faster to debug problems when just including the driver's euphoria code directly. (If testing multiple drivers natively, just use namespaces to avoid conflicts.)
Here is the diff for the changes I made to allow using edbi_eusql natively: http://euphoria.pastey.net/126630
I discovered a bug in edbi_eusql.e, edbi_next() should take two paramenters (dbr and row) but only took one.
The diff file contains this one-liner as well.
