FreeTDS Development Group

["Lowden, James K" <LowdenJK AT bernstein.com>]

> From: Harrison, Bruce (CXO) [mailto:Bruce.Harrison AT hp.com]
> Sent: December 11, 2002 3:56 PM
> 
>     It appears that some time between November 22, 2002 and 
> today, some
> of the tds_* function definitions have changed.  

Bruce, 

I think what you're seeing is Frediano's response to your (friendly)
complaint about warnings from the aCC compiler.  Either that, or he's
cleaning up similar warnings from Microsoft's compiler.  

> It this documented somewhere?  

Surely.  The distribution includes a file "ChangeLog", containing a
meticulous recapitulation of changed files.  In addition, the sources are in
CVS, which is accessible both anonymously and via the web.  

> Below are a couple of examples that the compiler 
> complained about in my code.  

What means "complained"?  There were warnings before; there should be fewer
now.  If we broke something (errors) on your compiler, please post the error
messages (or a patch) so we can repair them.  You seem to have one of the
fussier models out there, which can help us clean things up.  For instance,
I don't know how to make gcc complain if an "unsigned char *" is passed to
strcpy(3).  Not that I think it should, mind.  

> Maybe I somehow got an old kit on 11/22/02???

I don't think so.  Work is ongoing.  We don't attempt to document (beyond
what I mentioned above) the changes to the tds library.  It's there to help
us, and when it's being unhelpful, we change it without ceremony.  

--jkl


The information contained in this transmission may contain privileged and
confidential information and is intended only for the use of the person(s)
named above.  If you are not the intended recipient, or an employee or agent
responsible for delivering this message to the intended recipient, any
review, dissemination, distribution or duplication of this communication is
strictly prohibited. If you are not the intended recipient, please contact
the sender immediately by reply e-mail and destroy all copies of the
original message. Please note that we do not accept account orders and/or
instructions by e-mail, and therefore will not be responsible for carrying
out such orders and/or instructions.