On Wed, May 29, 2002 at 08:59:01AM +0200, H.Merijn Brand wrote: > On Tue 28 May 2002 03:33, Jarkko Hietaniemi <[EMAIL PROTECTED]> wrote: > > DBD::Oracle > > Short story: > > All tests successfull > > Long story: > > cc: "Oracle.xs", line 69: warning 563: Argument #1 is not the correct type. > cc: "Oracle.xs", line 79: warning 604: Pointers are not assignment-compatible. > cc: "Oracle.xs", line 79: warning 563: Argument #1 is not the correct type. > cc: "Oracle.xs", line 83: warning 604: Pointers are not assignment-compatible. > cc: "Oracle.xs", line 83: warning 563: Argument #1 is not the correct type. > cc: "Oracle.xs", line 86: warning 604: Pointers are not assignment-compatible. > cc: "Oracle.xs", line 86: warning 563: Argument #1 is not the correct type.
[After a quick look] this will affect any DBI drivers that are still using fprintf() for trace messages instead of PerlIO_vfprintf. (I haven't made a release of DBD::Oracle since August 2001. I hope to soon - and this is certainly a good incentive.) Meanwhile, the driver will work so long as you don't enable tracing... Tim.
