From: "Eli Zaretskii" <eliz@gnu.org>
To: Baurzhan Ismagulov <ibr@radix50.net>
Cc: gdb-patches@sources.redhat.com
Subject: Re: i18n, part 3
Date: Sat, 29 Jan 2005 17:22:00 -0000 [thread overview]
Message-ID: <01c50626$Blat.v2.4$9214fca0@zahav.net.il> (raw)
In-Reply-To: <20050129154549.GA9491@radix50.net> (message from Baurzhan Ismagulov on Sat, 29 Jan 2005 16:45:49 +0100)
> Date: Sat, 29 Jan 2005 16:45:49 +0100
> From: Baurzhan Ismagulov <ibr@radix50.net>
>
> On Thu, Jan 20, 2005 at 11:10:31PM +0200, Eli Zaretskii wrote:
> > > Is the following declaration near the end of ax-gdb.c unnecessary?
> > >
> > > void _initialize_ax_gdb (void);
> >
> > No, it isn't unnecessary (under certain command-line options, GCC will
> > whine if it sees a function definition without a prototype anywhere in
> > scope).
>
> Do you mean -Wmissing-prototypes? If the goal is to detect API functions
> not declared in headers, then I'm not sure whether this human work can
> be done by the compiler. Apparently, for some reason this function
> doesn't need to be declared in the header. What is the point using this
> option, then?
I think we want our sources to compile under any combination of the
"-Wsomething" options, even the most paranoiac ones.
> > Should we have an i18n comment here explaining what's a pcb? (You did
> > that elsewhere in the patch.)
>
> Hmm, I thought one time would suffice. But ok, let's create a luxurious
> messages file this time :) .
Thanks, your new version is okay with me.
next prev parent reply other threads:[~2005-01-29 17:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-19 22:25 Baurjan Ismagulov
2005-01-20 21:14 ` Eli Zaretskii
2005-01-29 15:50 ` Baurzhan Ismagulov
2005-01-29 17:22 ` Eli Zaretskii [this message]
2005-01-29 17:55 ` Baurzhan Ismagulov
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='01c50626$Blat.v2.4$9214fca0@zahav.net.il' \
--to=eliz@gnu.org \
--cc=gdb-patches@sources.redhat.com \
--cc=ibr@radix50.net \
/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