Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Andrew Cagney <ac131313@cygnus.com>
To: Kevin Buettner <kevinb@cygnus.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [PATCH RFA] utils.c: Fix xcalloc (0, 0) behavior
Date: Mon, 05 Mar 2001 12:28:00 -0000	[thread overview]
Message-ID: <3AA3F64E.9F0302A5@cygnus.com> (raw)
In-Reply-To: <1010303075808.ZM24102@ocotillo.lan>

Kevin Buettner wrote:
> 
> According to section 16.1 in Harbison & Steele, it is permissible for
> calloc(0,0) to return either NULL or an implementation defined unique
> pointer.  I've come across an implementation of calloc() which chooses
> to return NULL.

Does anyone know what the ISO-C standard has to say?  I think it would
be helpful if xcalloc() not only followed ISO-C but also did it in a
consistent way across platforms.

nice catch,

	Andrew


  parent reply	other threads:[~2001-03-05 12:28 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1010303075808.ZM24102@ocotillo.lan>
2001-03-03  0:02 ` Kevin Buettner
2001-03-05 12:28 ` Andrew Cagney [this message]
2001-03-05 12:39   ` J.T. Conklin
2001-03-05 12:51   ` Kevin Buettner
2001-03-05  7:52 David Taylor

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=3AA3F64E.9F0302A5@cygnus.com \
    --to=ac131313@cygnus.com \
    --cc=gdb-patches@sources.redhat.com \
    --cc=kevinb@cygnus.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox