freetds AT lists.ibiblio.org
Subject: FreeTDS Development Group
List archive
- From: "Castellano, Nicholas" <Nicholas_Castellano AT acml.com>
- To: "'TDS Development Group'" <freetds AT franklin.metalab.unc.edu>
- Subject: Re: const
- Date: Mon, 4 Nov 2002 16:57:57 -0500
Good...glad you agree. Hopefully nobody else will object and I can go ahead
with this soon.
By the way, your change to dblib.c is not really appropriate. It does not
really correct these warnings, it just hides them a little bit better. If
you use "-Wcast-qual" you will still receive a warning. The correct fix is
to go ahead with my suggestion and add "const" in the appropriate places in
the public interfaces, so that these items are passed consistently between
all functions as const.
Cheers,
--nick
-----Original Message-----
From: bounce-freetds-145195 AT franklin.oit.unc.edu
[mailto:bounce-freetds-145195 AT franklin.oit.unc.edu]
Sent: Monday, November 04, 2002 3:49 PM
To: TDS Development Group
Subject: [freetds] Re: const
No, placing constant here is not a problem nor for caller (char* can always
be converted to const char* and without explicit cast of
warnings) nor for library implementation/compatibility (C has no name
mangling like C++, so internal function name is the same)
---
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.
- const, Castellano, Nicholas, 11/04/2002
Archive powered by MHonArc 2.6.24.