NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.
All the Perl that's Practical to Extract and Report
use Perl Log In
Matts (1087)
Matts
(email not shown publicly)
I work for MessageLabs [messagelabs.com] in Toronto, ON, Canada. I write spam filters, MTA software, high performance network software, string matching algorithms, and other cool stuff mostly in Perl and C.
(email not shown publicly)
I work for MessageLabs [messagelabs.com] in Toronto, ON, Canada. I write spam filters, MTA software, high performance network software, string matching algorithms, and other cool stuff mostly in Perl and C.
Monday August 02, 2004
01:48 PM
DBD::SQLite
I just put out 1.02 of DBD::SQLite. It's a bug fix against 1.01 because old compilers don't like you declaring variables after calling a function in a particular scope, and I'd just messed up on that. 1.01 fixed a few things to do with calling the same statement twice.
My only problem now is that I'm using the following macro:
#define sqlite_trace(level,fmt...) _sqlite_tracef(__FILE__, __LINE__, level, fmt)
which is valid under GCC, but not other compilers. Does anyone know how to define varargs macros in a cross platform manner?
DBD::SQLite
More |
Login
| Reply
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
--Larry Wall in stab.c from the perl source code
Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.
Samba does it like this (Score:2)
I remember seeing this done in Samba, but it's a nuisance, as you have to put all the varargs bits inside another set of parentheses.
Have a look at debug.h [samba.org] for details.
-Dom