Received: from u1.abs.net (root@u1.abs.net [207.114.0.131]) by hub.org (8.8.8/8.7.5) with ESMTP id TAA11998 for ; Thu, 16 Apr 1998 19:07:39 -0400 (EDT) Received: from insightdist.com (nobody@localhost) by u1.abs.net (8.8.5/8.8.5) with UUCP id SAA27258 for pgsql-interfaces@postgreSQL.org; Thu, 16 Apr 1998 18:43:58 -0400 (EDT) X-Authentication-Warning: u1.abs.net: nobody set sender to insightdist.com!byronn using -f Received: by insightdist.com (AIX 3.2/UCB 5.64/4.03) id AA15781; Thu, 16 Apr 1998 18:36:42 -0400 Received: from [3.0.0.50] by ceodev (AIX 4.1/UCB 5.64/4.03) id AA59540; Thu, 16 Apr 1998 18:30:21 -0400 Message-Id: <3536874E.A8DB4B2@insightdist.com> Date: Thu, 16 Apr 1998 18:33:50 -0400 From: Byron Nikolaidis X-Mailer: Mozilla 4.05 [en] (Win95; I) Mime-Version: 1.0 To: "Julia A.Case" , pgsql-interfaces Subject: Re: Small patch to compile clean against VC++ 5.0 References: <3534EF3C.51C85C7@insightdist.com> <19980415131528.32791@MageNet.com> <3535075F.8A7A996@insightdist.com> <35352999.3FD27EDE@insightdist.com> <19980415210727.17671@MageNet.com> <35365FD8.EEDABF83@insightdist.com> <19980416151101.49473@MageNet.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Julia, I made all the patches to let it compile clean on MS VC 5.0 I reworked some things with the order of the wonderful Microsoft header files so that the Q_LOG can remain compiled in yet the driver compiles clean. I'll put the latest stuff on the web site still until I hear otherwise. Regards, Byron Julia A.Case wrote: > Quoting Byron Nikolaidis (byronn@insightdist.com): > > Julia, > > > > I would like to make it compile on 5.0 also, I just have a couple of questions about this patch: > > > > > - result = SQLGetData(hstmt, 1, SQL_C_SLONG, &self->lobj_type, sizeof(self->lobj_type), NULL); > > > + result = SQLGetData(hstmt, 1, SQL_C_LONG, &self->lobj_type, sizeof(self->lobj_type), NULL); > > > > SQL_C_SLONG is the ODBC 2.0 type to use and should be in sql.h; SQL_C_LONG is a ODBC 1.0 type. > > > Perhaps there was another missing ??? > > > > -#define Q_LOG > > > +// #define Q_LOG > > > > > > > > > > Why would this cause a problem? This is to compile in the communications log feature which is quite > > useful and was wanted for a long time. If it is commented out like you have shown it, it could not be > > activated from the setup dialog boxes. > > > > Do these things cause warnings or errors? > > > the va_args macros cause errors... and to be honest I don't know > enough to fix them, so it seemed simpler to comment them out. Will that > many END users be using Q_LOG? I'd think that would mostly be a developer > thing... and if so, a developer could uncomment it if they wanted it. > > Julie > > -- > [ Julia Anne Case ] [ Ships are safe inside the harbor, ] > [Programmer at large] [ but is that what ships are really for. ] > [ Admining Linux ] [ To thine own self be true. ] > [ Windows/WindowsNT ] [ Fair is where you take your cows to be judged. ]