From: Joel Brobecker <brobecker@gnat.com>
To: Aidan Skinner <aidan@velvet.net>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [patch] change knr function definitions in ada-lang.c, ada-typeprint.c, ada-valprint.c
Date: Thu, 25 Jul 2002 03:13:00 -0000 [thread overview]
Message-ID: <20020725064127.GA683@gnat.com> (raw)
In-Reply-To: <20020725021316.C10346@velvet.net>
Aidan,
> 2002-07-24 Aidan Skinner <aidan@velvet.net>
>
> * ada-lang.c: Change k&r style function definitions to prototyped
> form.
> * ada-typeprint.c: Change k&r style function definitions to prototyped
> form.
> * ada-valprint.c: Change k&r style function definitions to prototyped
> form.
I have a few minor comments, and I think I have also found a couple of
little ooopsies.
| + value_from_contents_and_address (struct type* type, char* valaddr, CORE_ADDR address)
This line is more than 80 characters long. I don't know if this is a
requirement in the GDB coding standards (did not find any mention of
it in the GDB internal documentation), but I personally prefer it when
long lines are broken up. Is there a consensus on this topic?
Same comment for the following functions:
[in ada-lang.c]
- ada_update_initial_language
- ada_lookup_struct_elt_type
- can_discrim_bound
- ada_value_ptr_subscript
- ada_array_bound_from_type
- ada_resolve_subexp
- ada_convert_actuals
- ada_lookup_partial_symbol
- add_symbols_from_enclosing_procs
- ada_lookup_symbol
[in ada-typeprint.c]
- ada_typedef_print
- print_range_bound
- print_dynamic_range_bound
- print_array_type
- print_choices
- print_record_type
| +ada_lookup_partial_symbol (struct partial_symtab *pst, const char *name, int global, namespace_enumnamespace, int wild)
There is a space missing between namespace_enum and namespace.
| -ada_array_element_type (type, nindices)
| - struct type* type;
| - int nindices;
| +ada_array_element_type (struct btype* type, int nindices)
Is the change from "struct type" to "struct btype" intended?
--
Joel
next prev parent reply other threads:[~2002-07-25 6:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-24 18:33 Aidan Skinner
2002-07-25 3:13 ` Joel Brobecker [this message]
2002-07-25 11:47 ` Andrew Cagney
2002-08-11 10:02 ` Aidan Skinner
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=20020725064127.GA683@gnat.com \
--to=brobecker@gnat.com \
--cc=aidan@velvet.net \
--cc=gdb-patches@sources.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