home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!crdgw1!rpi!usc!howland.reston.ans.net!spool.mu.edu!agate!doc.ic.ac.uk!pipex!demon!trmphrst.demon.co.uk!nikki
- From: nikki@trmphrst.demon.co.uk (Nikki Locke)
- Newsgroups: comp.lang.c++
- Subject: Re: Possible bug in BC 3.1: ellipsis in proto argument list
- Message-ID: <728160066snx@trmphrst.demon.co.uk>
- Date: 27 Jan 93 11:41:06 GMT
- References: <1993Jan24.050155.32517@ns1.cc.lehigh.edu>
- Sender: usenet@demon.co.uk
- Reply-To: nikki@trmphrst.demon.co.uk
- Organization: Trumphurst Ltd.
- Lines: 14
- X-Mailer: cppnews $Revision: 1.31 $
-
- In article <1993Jan24.050155.32517@ns1.cc.lehigh.edu> sg0d@ns1.cc.lehigh.edu (STEPHEN R. GILBERT) writes:
- > I seem to have found a bug in my Borland C++ 3.1 compiler. I narrowed
- > the problem down to the following prototype:
- >
- > void foo(...)
-
- This prototype is not useful in ANSI C, as there is no way to access any
- of the arguments of foo. The ANSI C stdargs mechanism cannot be used
- unless there is at least one fixed argument. This is perhaps why you have
- a problem.
-
- --
- Nikki Locke,Trumphurst Ltd.(PC and Unix consultancy) nikki@trmphrst.demon.co.uk
- trmphrst.demon.co.uk is NOT affiliated with ANY other sites at demon.co.uk.
-