From: Seth Alves <alves@hungry.com>
To: kawa@sourceware.org
Subject: Re: writing to parameter / type-switch
Date: Sat, 29 Nov 2014 18:26:00 -0000 [thread overview]
Message-ID: <547A0FCA.2030008@hungry.com> (raw)
In-Reply-To: <547A0B5E.9060206@bothner.com>
On 11/29/2014 10:07 AM, Per Bothner wrote:
>
> I'm not considering this a high-priority bug because of the easy
> work-around and
> because frankly I consider the example pretty horrible style ...
Agreed. This code is from... 1995. I'll file a bug report.
-seth
prev parent reply other threads:[~2014-11-29 18:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-29 15:09 Seth Alves
2014-11-29 18:07 ` Per Bothner
2014-11-29 18:26 ` Seth Alves [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=547A0FCA.2030008@hungry.com \
--to=alves@hungry.com \
--cc=kawa@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).