freetds AT lists.ibiblio.org
Subject: FreeTDS Development Group
List archive
- From: "ZIGLIO, Frediano, VF-IT" <Frediano.Ziglio AT vodafone.com>
- To: "FreeTDS Development Group" <freetds AT lists.ibiblio.org>
- Subject: [freetds] malloc/errno portability considerations
- Date: Wed, 5 Dec 2007 17:11:30 +0100
I this that a line like
dbperror(NULL, SYBEMEM, errno);
is not that portable. The reason is that not all malloc implementations
set errno with ENOMEM. Why should replace the above line with
dbperror(NULL, SYBEMEM, ENOMEM);
freddy77
-
[freetds] malloc/errno portability considerations,
ZIGLIO, Frediano, VF-IT, 12/05/2007
- Re: [freetds] malloc/errno portability considerations, James K. Lowden, 12/05/2007
-
Re: [freetds] malloc/errno portability considerations,
Christos Zoulas, 12/05/2007
- Re: [freetds] malloc/errno portability considerations, Reid, Roger L., 12/07/2007
Archive powered by MHonArc 2.6.24.