Skip to Content.
Sympa Menu

freetds - Re: Coding style document

freetds AT lists.ibiblio.org

Subject: FreeTDS Development Group

List archive

Chronological Thread  
  • From: "Brian Bruns" <camber AT ais.org>
  • To: freetds AT franklin.oit.unc.edu
  • Subject: Re: Coding style document
  • Date: Fri, 14 Jun 2002 10:56:56 -0400


Actually after all the changes to the convert function this is only used
for bit and int[1,2,4]. This could actually be made an automatic value in
each of those functions (and could be much shorter in length anyway).

I doubt I'll be able to patch it today, and I'll be out of town until
monday starting tomorrow morning. Hopefully, I can get to it after that.

Brian

> On 2002.06.13, James K. Lowden <jklowden AT speakeasy.org> wrote:
> > On Thu, 13 Jun 2002 16:12:56 -0400 "Dossy" <dossy AT panoptic.com> wrote:
> >
> > > While we're at it, in a greedy fit of self-interest, can I ask that
> > > thread-safe versions of the convert functions be created, so I can
> > > ditch the ones I hacked together for nsfreetds?
> >
> > I have a thread-poor system. Could you be more explicit about what's not
> > thread-safe in convert.c? I'm familiar with threading issues in general,
> > but not with the unix system calls or structure names.
>
> convert.c:
>
> 56 /*
> 57 this needs to go...
> 58 it won't handle binary or text/image when they are added
> 59 it's not thread safe
> 60 it works for the moment though til i decide how i really want to
> handle it
> 61 */
> 62 static TDS_CHAR tmp_str[4096];
>
> Global variables are not thread-safe.
>
> I just found this URL about "Writing Reentrant and Thread-Safe Code"
> which might be worth a quick read:
>
>
> http://www.unet.univie.ac.at/aix/aixprggd/genprogc/writing_reentrant_thread_safe_code.htm
>
> -- Dossy




Archive powered by MHonArc 2.6.24.

Top of Page