public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: Phil Prentice <philp.cheer@btinternet.com>
To: gcc-help@gnu.org
Subject: varargs
Date: Thu, 15 Apr 2004 19:35:00 -0000	[thread overview]
Message-ID: <E1BECNu-0002zk-00@zinc.btinternet.com> (raw)

Hi

  We are currently porting software using the gnu compiler (3.3.3).  Its 
working very well so far, but we have a problem over varargs.

  There are dozens of files which use varargs (not stdarg).  In time we will 
move these files over to use stdarg, however we have the added problem of 
there having to be at least one parameter being declared for stdarg to 
compile and work.

  1)  Is there anyway that we can cheat here  or do we have to go through all 
the function calls and add a dummy parameter etc to enable us to use 
stdarg's??  Many of these functions accept 0 or more tag parameters. How do 
we cope with no parameters?

   2) Same question really, but a considerably amount of software exists  
which interfaces to our varargs software which would be nia on impossible to 
change.  Again in this case are we stuck to having to use an older version of 
the compiler which supports varargs or again can we cheat somehow?

  3)  What is the latest version of the compiler that still supports varargs?

  It would be nice to use stdarg but without the worry of changing the 
calling software?  Is there any way around the problem of zero parameters?


Thanks again for all your help

  Phil

             reply	other threads:[~2004-04-15 19:35 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-15 19:35 Phil Prentice [this message]
2004-04-15 20:56 ` varargs llewelly
2007-06-26  4:41 varargs Constantine Kousoulos
2007-06-28  5:25 ` varargs Ian Lance Taylor

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=E1BECNu-0002zk-00@zinc.btinternet.com \
    --to=philp.cheer@btinternet.com \
    --cc=gcc-help@gnu.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).