From: Jeffrey A Law <law@cygnus.com>
To: hjl@lucon.org (H.J. Lu)
Cc: egcs@cygnus.com
Subject: Re: No prototype for is_java_type
Date: Sun, 10 May 1998 02:05:00 -0000 [thread overview]
Message-ID: <16781.894782552@hurl.cygnus.com> (raw)
In-Reply-To: <m0yXq1l-000268C@ocean.lucon.org>
In message < m0yXq1l-000268C@ocean.lucon.org >you write:
> > If you'd take a look the one patch that you "un-megaized" did go in after
> > I fixed several problems with it (rtl.h prototyping).
> >
>
> Before I send in many patches, what about the format of prototype?
> I have seen many different ones for the new prototypes:
>
> extern int foo PROTO((void));
> extern int foo PROTO ((void));
> extern int foo PROTO ((void));
> extern int foo PROTO((void));
Either the second or third is the preferred format. I personally
prefer the 3rd since it makes it much easier to read (IMHO).
It is also acceptable to format a prototype in a format identical to
those around it. This is strictly a readability issue -- it does
not make much sense to have 20 consecutive prototypes of one format,
then one outlier of a different format.
jeff
prev parent reply other threads:[~1998-05-10 2:05 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-05-07 17:39 A patch for g++ Andrew Macleod
1998-05-07 21:59 ` No prototype for is_java_type H.J. Lu
1998-05-07 23:40 ` Jeffrey A Law
1998-05-08 7:55 ` H.J. Lu
1998-05-08 9:29 ` Jeffrey A Law
1998-05-08 9:29 ` H.J. Lu
1998-05-10 2:05 ` Jeffrey A Law [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=16781.894782552@hurl.cygnus.com \
--to=law@cygnus.com \
--cc=egcs@cygnus.com \
--cc=hjl@lucon.org \
/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).