From: Daniel Jacobowitz <drow@false.org>
To: lode lathouwers <lathouwers_lode@yahoo.co.uk>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] New maintenance print typechain command.
Date: Sat, 07 Apr 2007 17:39:00 -0000 [thread overview]
Message-ID: <20070407173919.GE24650@caradoc.them.org> (raw)
In-Reply-To: <130247.15914.qm@web28011.mail.ukl.yahoo.com>
On Wed, Apr 04, 2007 at 02:37:18PM +0000, lode lathouwers wrote:
> hi
> this is my first patch ever to an open source project , so probably I am doing some things wrong here ...
> Anyway attached you find some changes to add an extra print typechain command, which is like typechain, but instead of printing the internal nodes in the raw format it prints them in c-format.
> This is handy when we want to extract some type declarations from a series of headerfiles, and generate a header file only containing the declarations for those types. Afterwards, we could for example use the file in swig to generate interfaces towards other programming languages.
Do you mean you're parsing the output of the maintenance command
to create your header? I think that's a bad idea; the maint commands
are intended for GDB developers to use while debugging GDB.
Why can't you get what you need from 'info types'?
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2007-04-07 17:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-04 14:37 lode lathouwers
2007-04-07 17:39 ` Daniel Jacobowitz [this message]
2007-04-08 18:51 lode lathouwers
2007-04-10 14:03 ` Daniel Jacobowitz
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=20070407173919.GE24650@caradoc.them.org \
--to=drow@false.org \
--cc=gdb-patches@sourceware.org \
--cc=lathouwers_lode@yahoo.co.uk \
/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