From: Eli Zaretskii <eliz@gnu.org>
To: Tom Tromey <tromey@redhat.com>
Cc: a.kitouni@gmail.com, gdb-patches@sourceware.org
Subject: Re: Re : New language support : Vala
Date: Tue, 14 Apr 2009 07:21:00 -0000 [thread overview]
Message-ID: <8363h7og4d.fsf@gnu.org> (raw)
In-Reply-To: <m3prfgjcy2.fsf@fleche.redhat.com>
> Cc: gdb-patches@sourceware.org
> From: Tom Tromey <tromey@redhat.com>
> Date: Mon, 13 Apr 2009 18:28:37 -0600
>
> Tom> I don't know whether your FSF paperwork has gone through. I don't
> Tom> have a way to look that up any more; maybe someone else could find
> Tom> out.
>
> Abderrahim> Yes, I received the letter.
>
> Ok. The important bit for us is knowing when the FSF says that you
> are all set up.
I see that Abderrahim's name is already on file in the FSF copyright
assignments list.
> + TYPE_CODE (type =
> + check_typedef (TYPE_TARGET_TYPE (type))) == TYPE_CODE_STRUCT)
>
> GNU style prohibits embedded assignments like this.
Only inside an `if', which this one is not:
Try to avoid assignments inside `if'-conditions (assignments inside
`while'-conditions are ok). For example, don't write this:
if ((foo = (char *) malloc (sizeof *foo)) == 0)
fatal ("virtual memory exhausted");
instead, write this:
foo = (char *) malloc (sizeof *foo);
if (foo == 0)
fatal ("virtual memory exhausted");
That doesn't necessarily mean I'm opposed to Tom's comment, though:
unnecessary use of this style makes the source somewhat harder to
read.
> I know it is a pain, but this really needs test cases and
> documentation -- documentation for the users, and test cases so the
> gdb developers can test it occasionally. ("Occasionally" since I
> assume most of us won't have the vala compiler installed.)
I think such an important new feature will also need an entry for
NEWS.
Thanks.
prev parent reply other threads:[~2009-04-14 7:21 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-07 14:07 Abderrahim KITOUNI
2009-02-07 19:43 ` Tom Tromey
2009-02-09 13:05 ` Abderrahim KITOUNI
2009-02-19 8:29 ` Re : " Abderrahim KITOUNI
2009-02-24 19:58 ` Tom Tromey
2009-03-06 18:44 ` Abderrahim KITOUNI
2009-04-14 0:29 ` Tom Tromey
2009-04-14 7:21 ` Eli Zaretskii [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=8363h7og4d.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=a.kitouni@gmail.com \
--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