On Mon, Oct 20, 2003 at 07:15:11PM -0700, Dean Arnold wrote:
Coupla points:
1. After (painful) experimentation with Inline::Struct, I've determined
it's got some significant short comings at this time heavy sigh
2. Howver, for my purposes, with Inline::C and some clever editting
(thank
I'm dealing with a *very primitive* API. It operates at a level
only *slightly* above socket calls. (Which is why I wrote
a Pure Perl version of the driver in the first place).
Eg, in order to support simple things
like placeholders, a signifcant parse of the SQL is required
(the DBMS supports 2
On Tue, Oct 21, 2003 at 10:57:22AM -0700, Dean Arnold wrote:
All that being said, I seem to have inflamed a sore nerve.
Not at all. It wasn't clear what the underlying api was like.
From what you describe it _would_ make sense to first implement a
separate module providing a thin Perl
Tim Bunce wrote:
On Tue, Oct 21, 2003 at 10:57:22AM -0700, Dean Arnold wrote:
From what you describe it _would_ make sense to first implement a
separate module providing a thin Perl interface to the API, and
then implement a pure-perl driver that uses that.
Dean,
I'm working on the thinist
Tim Bunce wrote:
On Tue, Oct 21, 2003 at 10:57:22AM -0700, Dean Arnold wrote:
From what you describe it _would_ make sense to first implement a
separate module providing a thin Perl interface to the API, and
then implement a pure-perl driver that uses that.
Dean,
I'm working on
