From: Stefan Kristiansson <stefan.kristiansson@saunalahti.fi>
To: "Frank Ch. Eigler" <fche@elastic.org>
Cc: Stefan Kristiansson <stefan.kristiansson@saunalahti.fi>,
cgen@sourceware.org, Alan Modra <amodra@gmail.com>,
fche@sourceware.org, Christian Svensson <blue@cmd.nu>,
Pierre Muller <pierre.muller@ics-cnrs.unistra.fr>,
"Maciej W. Rozycki" <macro@codesourcery.com>
Subject: Re: [PATCH] Make large enum constants unsigned
Date: Thu, 22 May 2014 17:34:00 -0000 [thread overview]
Message-ID: <CADzBsGN3U6a3BS5L7o7DYh_4KTghEXnB2UE0XKdNZrAN=A0p=g@mail.gmail.com> (raw)
In-Reply-To: <20140522150956.GC4031@elastic.org>
On Thu, May 22, 2014 at 6:09 PM, Frank Ch. Eigler <fche@elastic.org> wrote:
> Have you thought of having cgen emit it as
>
> (string-append "(signed int)" (number->string (cadr e)))
>
Ignoring the 'string-upcase' that would turn that into "(SIGNED INT)",
how would that be better than?
(string-append (number->string (cadr e)) "U")
I dismissed that, since it would create a lot larger diff in generated
files than in the isolated cases where it's actually a problem.
> ... or even find a number->string conversion function that takes into
> account the destionation language's encoding constraints.
>
That might certainly be an option, but way over my current Scheme capabilities.
If you give me some pointers I could try to improve them.
Stefan
next prev parent reply other threads:[~2014-05-22 17:34 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-22 5:30 Stefan Kristiansson
2014-05-22 6:22 ` Maciej W. Rozycki
2014-05-22 6:52 ` Stefan Kristiansson
2014-05-22 7:10 ` Stefan Kristiansson
2014-05-22 13:33 ` Pierre Muller
[not found] ` <5561926758764771034@unknownmsgid>
2014-05-22 14:10 ` Stefan Kristiansson
2014-05-22 16:14 ` Maciej W. Rozycki
2014-05-22 15:11 ` Frank Ch. Eigler
2014-05-22 17:34 ` Stefan Kristiansson [this message]
2014-05-22 21:06 ` Frank Ch. Eigler
2014-05-22 21:42 ` Maciej W. Rozycki
2014-05-22 22:20 ` Frank Ch. Eigler
2014-05-29 20:09 ` Stefan Kristiansson
2014-05-29 20:32 ` Frank Ch. Eigler
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='CADzBsGN3U6a3BS5L7o7DYh_4KTghEXnB2UE0XKdNZrAN=A0p=g@mail.gmail.com' \
--to=stefan.kristiansson@saunalahti.fi \
--cc=amodra@gmail.com \
--cc=blue@cmd.nu \
--cc=cgen@sourceware.org \
--cc=fche@elastic.org \
--cc=fche@sourceware.org \
--cc=macro@codesourcery.com \
--cc=pierre.muller@ics-cnrs.unistra.fr \
/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).