From: Iain Buclaw <ibuclaw@gdcproject.org>
To: Tom Tromey <tromey@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH 4/5] Implement D primitive types in GDB
Date: Thu, 09 Jan 2014 18:41:00 -0000 [thread overview]
Message-ID: <CABOHX+cCjqr6-YdK9jhBu+aM623hWM-RgG113PxpsP-F=LoHvg@mail.gmail.com> (raw)
In-Reply-To: <87sisx80oo.fsf@fleche.redhat.com>
On 9 January 2014 18:33, Tom Tromey <tromey@redhat.com> wrote:
>>>>>> "Iain" == Iain Buclaw <ibuclaw@gdcproject.org> writes:
>
> Iain> D has it's own type system separate from C. This defines all
> Iain> primitive types all found in D.
>
> Thanks. I think the guts of this patch are fine, just some nits around
> the edges.
>
>
> Iain> +enum d_primitive_types {
>
> Comment before the new type.
>
> Iain> + d_primitive_type_cent,
> Iain> + d_primitive_type_ucent,
>
> I don't think we need a comment for each enum constant, but it would be
> nice for the ones that are "not obvious to C developers". Subjective I
> realize; but at least here I have no idea what "cent" means.
>
> Iain> + d_primitive_type_ifloat,
> Iain> + d_primitive_type_idouble,
> Iain> + d_primitive_type_ireal,
>
> Or what the "i" prefix means.
>
> Iain> + d_primitive_type_cfloat,
> Iain> + d_primitive_type_cdouble,
> Iain> + d_primitive_type_creal,
>
> "c" means complex maybe?
>
Sure, not a problem. For reference, cent/ucent are 128bit types - not
actually implemented at all, but they have been kept around as
keywords for possible future use. The "i" prefix is for Imaginary
numbers, and the "c" prefix is for Complex numbers.
>
> Iain> +# NOTE: The tests here intentionally do not require a go compiler.
>
> Cut-and-pasto :)
>
Aww..... :-)
next prev parent reply other threads:[~2014-01-09 18:41 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-09 13:11 Iain Buclaw
2014-01-09 18:33 ` Tom Tromey
2014-01-09 18:41 ` Iain Buclaw [this message]
2014-01-10 12:57 ` Iain Buclaw
2014-01-10 21:18 ` Tom Tromey
2014-01-11 16:39 ` Iain Buclaw
2014-01-13 20:03 ` Tom Tromey
2014-01-18 18:23 ` Iain Buclaw
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='CABOHX+cCjqr6-YdK9jhBu+aM623hWM-RgG113PxpsP-F=LoHvg@mail.gmail.com' \
--to=ibuclaw@gdcproject.org \
--cc=gdb-patches@sourceware.org \
--cc=tromey@redhat.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).