[freetds] CS_INT size bug

michael.peppler at bnpparibas.com michael.peppler at bnpparibas.com
Mon Sep 4 02:02:52 EDT 2006

Actually Sybase defines different sizes for CS_INT depending on 32 or 64bit
wordsize for the platform. This is what the SYB_LP64 #define is for.

CS_INT must be 32bits as it maps to an INT database server datatype
(consider the ct_bind() call, for example).


jklowden at schemamania.org@lists.ibiblio.org - 04/09/2006 00:07

Please respond to freetds at lists.ibiblio.org

Sent by:    freetds-bounces at lists.ibiblio.org

To:    freetds


Subject:    Re: [freetds] CS_INT size bug

On Sun, Sep 03, 2006 at 04:42:12PM -0400, entropy at freetds.org wrote:
> Norbert Sendetzky wrote:
> > I'm using a standard 32bit x86 machine.
> >
> > The problem I'm facing are lots of warnings when compiling the sybase
> > of my library (OpenDBX, http://www.linuxnetworks.de/opendbx/) against
> > instead of the Sybase ctlib.
> >
> > In Sybase' ctlib, CS_INT is defined as "long" and as "int" in FreeTDS
which is
> > problematic when using printf() functions. This is because of the
> > expectations gcc/printf have when handling "%d" and "%ld" modifiers.
> The problem is that your code is making assumptions about what type a
> CS_INT is.  If it were reasonable for your code to do that, then there
> would be no such thing as a CS_INT, and instead it would just be "int"
> or "long".
> The most portable thing your code can do in this case is explicitly cast
> to a type, then use the printf(3) format for that type.

That's good advice from a C perspective.  The application shouldn't assume
anything about opaque types.

>From the library's perspective, though, maybe we're making a mistake?  We
do a bunch of things in the header files -- e.g. use #define instead of
-- just because that's how Sybase did it 20 years ago.  It wouldn't be
wrong to change it.

Thanks for pointing it out, Norbert.  I don't know what we'll do or what's
even feasible, but it's worth at least discussing.


FreeTDS mailing list
FreeTDS at lists.ibiblio.org

This message and any attachments (the "message") is
intended solely for the addressees and is confidential. 
If you receive this message in error, please delete it and 
immediately notify the sender. Any use not in accord with 
its purpose, any dissemination or disclosure, either whole 
or partial, is prohibited except formal approval. The internet
can not guarantee the integrity of this message. 
BNP PARIBAS (and its subsidiaries) shall (will) not 
therefore be liable for the message if modified. 


Ce message et toutes les pieces jointes (ci-apres le 
"message") sont etablis a l'intention exclusive de ses 
destinataires et sont confidentiels. Si vous recevez ce 
message par erreur, merci de le detruire et d'en avertir 
immediatement l'expediteur. Toute utilisation de ce 
message non conforme a sa destination, toute diffusion 
ou toute publication, totale ou partielle, est interdite, sauf 
autorisation expresse. L'internet ne permettant pas 
d'assurer l'integrite de ce message, BNP PARIBAS (et ses
filiales) decline(nt) toute responsabilite au titre de ce 
message, dans l'hypothese ou il aurait ete modifie.

More information about the FreeTDS mailing list