Skip to Content.
Sympa Menu

freetds - RE: dberrhandler() and dbmsghandler()

freetds AT lists.ibiblio.org

Subject: FreeTDS Development Group

List archive

Chronological Thread  
  • From: "Lowden, James K" <LowdenJK AT bernstein.com>
  • To: "'TDS Development Group'" <freetds AT franklin.metalab.unc.edu>
  • Subject: RE: dberrhandler() and dbmsghandler()
  • Date: Fri, 6 Sep 2002 13:03:03 -0400


> From: Castellano, Nicholas [mailto:Nicholas_Castellano AT acml.com]
> Sent: September 6, 2002 12:02 PM
>
> In src/dblib/dblib.c we have definitions of dberrhandler() and
> dbmsghandler(). To me, these appear to do the same thing as
> dberrhandle() and dbmsghandle().
> According to the Sybase docs, the latter
> are the correct names. Should the former be deleted?

I think the "er" names should be removed, as you suggest.

The user-supplied function that handles the msg/err is the "handler". The
library function to install the handler is called a db...handle().
Microsoft's documentation is also consistent (!) in its terminology on this
point.

Aside: It seems to me that API-level changes of this sort should be
reflected in a RELEASE.NOTES file or similar. How do other projects do it?
I imagine a file in the source tree root that gradually accumulates changes
-- the kind of changes that might break or surprise existing code -- for
inclusion in the release. It would be carefully limited to describing new
behavior that would be encountered installing or testing an upgrade.

Nick, if you make this change before the weekend, I'll include it in the
release candidate.

--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 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