FreeTDS Development Group

["Thompson, Bill D (London)" <bill_d_thompson AT ml.com>]

Hi Freddy,

My installation of Sybase open client has a file called csconfig.h
which includes the following:

#if defined(__alpha)
typedef int     CS_INT;
typedef int     CS_RETCODE;
typedef int     CS_BOOL;
typedef unsigned int    CS_UINT;
#else
typedef long        CS_INT;
typedef long        CS_RETCODE;
typedef long        CS_BOOL;
typedef unsigned long   CS_UINT;
#endif

which is then included in cstypes.h, thus:

/*
** Include the configuration header file. This file contains the defines
and
** type definitions that are platform/compiler specific.
*/
#include    <csconfig.h>


I changed the definition of our CS_BOOL to match sybase's on my
platform.
What do you have on your installation of sybase open client ?

HTH,

Bill


-----Original Message-----
From: freetds-bounces AT lists.ibiblio.org
[mailto:freetds-bounces AT lists.ibiblio.org] On Behalf Of ZIGLIO,
Frediano, VF-IT
Sent: 21 September 2005 08:32
To: FreeTDS Development Group
Subject: [freetds] Sybase "binary" compatibility


Well, although is a bit hard to speak about binary compatibility for
ctlib I revised ctlib public headers to align declarations with Sybase
ones. This certainly improve binary compatibility but also break
existing 0.63 compatibility... The question is: should I commit this
change? Is better to support a configure switch to decide which headers
to use? I must say that 0.64 are not fully binary compatible with 0.63.
A small change (CS_BOOL is now int instead of unsigned char) make 0.64
not compatible. IMHO if we decide to change binary compatiblity we
should follow Sybase one so in a future we can hope to produce a full
compatible library.

freddy77
_______________________________________________
FreeTDS mailing list
FreeTDS AT lists.ibiblio.org
http://lists.ibiblio.org/mailman/listinfo/freetds
--------------------------------------------------------

If you are not an intended recipient of this e-mail, please notify the 
sender, delete it and do not read, act upon, print, disclose, copy, retain or 
redistribute it. Click here for important additional terms relating to this 
e-mail.     http://www.ml.com/email_terms/
--------------------------------------------------------