From: Stan Cox <scox@redhat.com>
To: Frysk List <frysk@sourceware.org>
Subject: Re: Use StringBuilder instead of PrintWriter for type display
Date: Mon, 10 Dec 2007 22:08:00 -0000 [thread overview]
Message-ID: <1197323992.10805.201.camel@multics.rdu.redhat.com> (raw)
In-Reply-To: <1197323542.10805.196.camel@multics.rdu.redhat.com>
I forgot to mention the primary difference is that the bottom up
approach in some cases (array dcls, ptr to functions) requires a token
to be inserted marker (%s) that later needs to be substituted. The top
down approach in some cases (parameter lists, struct members) requires a
temporary buffer.
prev parent reply other threads:[~2007-12-10 22:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-07 21:43 Stan Cox
2007-12-07 23:11 ` Andrew Cagney
2007-12-08 0:53 ` Andrew Cagney
2007-12-10 22:00 ` Stan Cox
2007-12-10 22:08 ` Stan Cox [this message]
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=1197323992.10805.201.camel@multics.rdu.redhat.com \
--to=scox@redhat.com \
--cc=frysk@sourceware.org \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).