On Fri, Feb 10, 2012 at 10:03:06AM -0800, Jan Dubois wrote:
On Fri, 10 Feb 2012, Tim Bunce wrote:
On Fri, Feb 10, 2012 at 03:27:24PM +, Dave Mitchell wrote:
If anyone knows of a more elegant way to make a function from DBI.xs
available to DBD:: code, please let me know!
I hope
On Fri, 17 Feb 2012, Dave Mitchell wrote:
On Fri, Feb 10, 2012 at 10:03:06AM -0800, Jan Dubois wrote:
On Fri, 10 Feb 2012, Tim Bunce wrote:
On Fri, Feb 10, 2012 at 03:27:24PM +, Dave Mitchell wrote:
If anyone knows of a more elegant way to make a function from
DBI.xs available to DBD::
On Fri, Feb 10, 2012 at 03:27:24PM +, Dave Mitchell wrote:
I'm assuming that these won't be applied until after the windows() fork
issue is fixed, so think of this email more as a preview.
The first fix is relatively straightforward, and is private to DBI.xs,
since the PERINTERP macros
On Thu, Jan 26, 2012 at 12:26:44PM +, Tim Bunce wrote:
On Wed, Jan 25, 2012 at 05:37:13PM -0800, Jan Dubois wrote:
On Wed, 25 Jan 2012, Tim Bunce wrote:
On Wed, Jan 25, 2012 at 04:14:07PM +, Dave Mitchell wrote:
PS - I'm specifically being paid only to fix a performance issue
On Fri, Feb 10, 2012 at 03:27:24PM +, Dave Mitchell wrote:
On Thu, Jan 26, 2012 at 12:26:44PM +, Tim Bunce wrote:
I attach two patches; the first replaces dPERINTERP with dMY_THX,
while the second extends this to the DBIS stuff too.
The headline figure (YMMV etc) is that on a
On Fri, 10 Feb 2012, Tim Bunce wrote:
On Fri, Feb 10, 2012 at 03:27:24PM +, Dave Mitchell wrote:
If anyone knows of a more elegant way to make a function from DBI.xs
available to DBD:: code, please let me know!
I hope to take a proper look in the next day or so.
The standard way
