Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Stan Shebs <shebs@cygnus.com>
To: cagney@cygnus.com
Cc: gdb@cygnus.com
Subject: Re: More gdb-4.17.85 testresults
Date: Thu, 01 Apr 1999 00:00:00 -0000	[thread overview]
Message-ID: <199903100246.SAA12486@andros.cygnus.com> (raw)
In-Reply-To: <36E4A175.DEA4FA72@cygnus.com>

   Date: Tue, 09 Mar 1999 15:20:06 +1100
   From: Andrew Cagney <ac131313@cygnus.com>

   > cc: "../../gdb-4.17.85/gdb/remote.c", line 3046: \
   >     error 1711: Inconsistent parameter list declaration for "remote_query".
   >

       static int remote_query PARAMS ((char, char *, char *, int *));

   and:

       static int
       remote_query (query_type, buf, outbuf, bufsiz)
	    char query_type;
	    char *buf;
	    char *outbuf;
	    int *bufsiz;

   This time I've no idea's as to what HP's ansic doesn't like about it.  Any
   suggestions?

The actual problem is that the function definition is "K&R style" not
true ANSI, but in any case the right solution is to change the first
arg from "char" to "int".  While there may be situations where you
really need an argument to be declared "char", in 20 years of C
programming I've only seen one case (certain Mac Toolbox calls) where
having a char arg was important, and dozens of cases where it just
made problems for no good reason.

(This one is a little embarassing, because I went over the remote_query
code, and missed it...)

								Stan


  parent reply	other threads:[~1999-04-01  0:00 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <9903039205.AA920520366.cygnus.gdb@cc.pmsc.com>
1999-04-01  0:00 ` Andrew Cagney
1999-04-01  0:00   ` Mike Vermeulen
1999-04-01  0:00   ` Stan Shebs [this message]
1999-04-01  0:00   ` Todd Whitesel
1999-04-01  0:00   ` Jim Blandy
     [not found] ` <npaexm4p27.fsf.cygnus.gdb@zwingli.cygnus.com>
1999-04-01  0:00   ` Andrew Cagney
1999-04-01  0:00 rodneybrown

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=199903100246.SAA12486@andros.cygnus.com \
    --to=shebs@cygnus.com \
    --cc=cagney@cygnus.com \
    --cc=gdb@cygnus.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