Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: "Pierre Muller" <muller@ics.u-strasbg.fr>
To: "Jim Blandy" <jimb@codesourcery.com>
Cc: gdb-patches@sourceware.org
Subject: Re: PATCH: Add 'static' keyword
Date: Wed, 25 Oct 2006 22:54:00 -0000	[thread overview]
Message-ID: <17854.57.67.16.50.1161816856.squirrel@websd.u-strasbg.fr> (raw)
In-Reply-To: <m3vem8dr1h.fsf@codesourcery.com>

   The problem is that I am not really a confirmed C code writer,
I basically started C programming to add pascal language
support in GDB.
   The same kind of error could be repeated in several
other locations, I did not even think that it was
a good practice to repeat 'static' in the implementation.

  Don't hesitate to correct others.


Pierre Muller

On Wed, October 25, 2006 23:27, Jim Blandy said:
>
> It's helpful when reading code to be able to see that a function is
> static simply looking at its definition.
>
> Committed as obvious.
>
> gdb/ChangeLog:
> 2006-10-25  Jim Blandy  <jimb@codesourcery.com>
>
> 	* p-valprint.c (pascal_object_print_value): Add 'static' keyword
> 	to function definition, to match declaration earlier in file.
>
> Index: gdb/p-valprint.c
> ===================================================================
> RCS file: /cvs/src/src/gdb/p-valprint.c,v
> retrieving revision 1.41
> diff -u -r1.41 p-valprint.c
> --- gdb/p-valprint.c	18 Jan 2006 21:24:19 -0000	1.41
> +++ gdb/p-valprint.c	25 Oct 2006 21:25:22 -0000
> @@ -915,7 +915,7 @@
>  /* Special val_print routine to avoid printing multiple copies of virtual
>     baseclasses.  */
>
> -void
> +static void
>  pascal_object_print_value (struct type *type, const gdb_byte *valaddr,
>  			   CORE_ADDR address, struct ui_file *stream,
>  			   int format, int recurse,
>


Pierre Muller
Institut Charles Sadron
aux Etats-Unis jusqu'à fin octobre 2006


  reply	other threads:[~2006-10-25 22:54 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-25 21:27 Jim Blandy
2006-10-25 22:54 ` Pierre Muller [this message]
2006-10-26 21:13   ` Jim Blandy

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=17854.57.67.16.50.1161816856.squirrel@websd.u-strasbg.fr \
    --to=muller@ics.u-strasbg.fr \
    --cc=gdb-patches@sourceware.org \
    --cc=jimb@codesourcery.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