FreeTDS Development Group

["Castellano, Nicholas" <Nicholas_Castellano AT acml.com>]

I have no idea what you mean by "there's no alias for cs_ctx_global to point
to cs_ctx_alloc."

We have a real, true, bonafide implementation of cs_ctx_global.

If you really used up-to-date code, you should not be having this problem.

So, either last night's snapshot is broken, or your setup is broken (maybe
you built the latest code but never installed it?  Or your Sybperl build is
finding an older FreeTDS installed in a different location?)

Cheers,
--nick

-----Original Message-----
From: bounce-freetds-145195 AT franklin.oit.unc.edu
[mailto:bounce-freetds-145195 AT franklin.oit.unc.edu]
Sent: Friday, October 25, 2002 1:49 PM
To: TDS Development Group
Subject: [freetds] Re: sybperl 2.15 again


"Lowden, James K" <LowdenJK AT bernstein.com> writes:

> cs_ctx_global() was implemented on 28 September, in revison 1.13 of
> cspublic.h.

Ah yes, but there's no alias for cs_ctx_global to point to
cs_ctx_alloc.

> Steven, if it's convenient, you might want to try a more recent snapshot.
I
> think Nick has addressed -- not to say fixed, but maybe -- all the issues
> you've raised so far.  No sense in you hacking on something else.  

I used last night's snapshot, so I'm up-to-date baby.

> But we don't have ct_poll; you'll have to stub that and see.  

Anyone want to stub this out for me?

Thanks,
  Steve

---
You are currently subscribed to freetds as: [Nicholas_Castellano AT acml.com]
To unsubscribe, forward this message to
$subst('Email.Unsub')


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.