Skip to Content.
Sympa Menu

freetds - RE: asprintf vasprintf

freetds AT lists.ibiblio.org

Subject: FreeTDS Development Group

List archive

Chronological Thread  
  • From: "Castellano, Nicholas" <Nicholas_Castellano AT acml.com>
  • To: "'TDS Development Group'" <freetds AT franklin.metalab.unc.edu>
  • Subject: RE: asprintf vasprintf
  • Date: Thu, 29 Aug 2002 13:06:30 -0400


The new version of the patch I sent today has no thread primitives.

On systems that already provide vasprintf() we already detect that in
autoconf and use it. This discussion is only about the thread-safety of our
replacement version, for systems that don't have it.

Now that Freddy applied my patch, I think we're done with this issue.

-----Original Message-----
From: bounce-freetds-145195 AT franklin.oit.unc.edu
[mailto:bounce-freetds-145195 AT franklin.oit.unc.edu]
Sent: Thursday, August 29, 2002 12:42 PM
To: TDS Development Group
Subject: [freetds] RE: asprintf vasprintf


I haven't been following this thread too closely, can someone give me a
quick summary on this? I'd rather not have any thread primitives in the
library if we can avoid it even if it does mean implementing our own on
those platforms that don't have a suitable reentrant function. And if we
have suitable functions on different platforms (Tru64 has X, linux has Y,
HP/UX has Z) can we wrap them and use autoconf to test?

Brian


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 for certain accounts we do not accept
orders and/or instructions by e-mail, and for those accounts we will not be
responsible for carrying out such orders and/or instructions. Kindly refrain
from sending orders or instructions by e-mail unless you have confirmed that
we accept such communications for your account. Please also note that to
satisfy regulatory requirements we review the outgoing and incoming e-mail
correspondence of staff members serving certain functions.






Archive powered by MHonArc 2.6.24.

Top of Page