Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Joel Brobecker <brobecker@adacore.com>
To: Pedro Alves <pedro@codesourcery.com>
Cc: gdb-patches@sourceware.org
Subject: Re: A couple of uses of xmalloc and xfree in a couple of .y files
Date: Sat, 25 Oct 2008 00:14:00 -0000	[thread overview]
Message-ID: <20081025001350.GC29998@adacore.com> (raw)
In-Reply-To: <200810242358.11089.pedro@codesourcery.com>

> Anything I'm missing preventing me from applying this as obvious?

Yes, I think we should be consistent.

The thing I don't get is why we don't translate free->xfree, though.

> 2008-10-24  Pedro Alves  <pedro@codesourcery.com>
> 
> 	* ada-exp.y (write_object_renaming): Use malloc instead of
> 	xmalloc.
> 	* p-exp.y (pop_current_type): Use free instead of xfree.

-- 
Joel


  reply	other threads:[~2008-10-25  0:14 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-24 22:58 Pedro Alves
2008-10-25  0:14 ` Joel Brobecker [this message]
2008-10-25  1:58   ` Daniel Jacobowitz
2008-10-25  2:37     ` Pedro Alves
2008-10-25  6:33       ` Daniel Jacobowitz
2008-10-25 15:54       ` Joel Brobecker
2008-10-27 11:48         ` Pedro Alves
2008-10-27 22:38           ` Pedro Alves

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=20081025001350.GC29998@adacore.com \
    --to=brobecker@adacore.com \
    --cc=gdb-patches@sourceware.org \
    --cc=pedro@codesourcery.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