In article <KAELIN.94Aug14105855@ignatz.bridge.com> kaelin@bridge.com (Kaelin Colclasure) writes:
>Amongst the noise on comp.lang.c++ I saw a post indicating that Watcom
>C++ doesn't support elipses (...) in declarations of virtual
>functions, and that this is prohibited in the current draft of the
>standard.  Is this fact (about the standard-- I'm less concerned about
>Watcom's compiler)?  If so, is there some rationale given?

I personally am not aware of such a rule (although that doesn't mean that
such a rule doesn't exist).

If there is such a rule, it seems that many implementors are not aware
of it either.  I just tried this:

struct S
{
  virtual void foobar (int arg, ...);
};

void S::foobar (int arg, ...)
{
}

on four different UNIX compilers and four different DOS compilers.  Watcom
was the only one that complained.

--

-- Ron Guilmette, Sunnyvale, CA ---------- RG Consulting -------------------
---- domain addr: rfg@netcom.com ----------- Purveyors of Compiler Test ----
---- uucp addr: ...!uunet!netcom!rfg ------- Suites and Bullet-Proof Shoes -

Amongst the noise on comp.lang.c++ I saw a post indicating that Watcom
C++ doesn't support elipses (...) in declarations of virtual
functions, and that this is prohibited in the current draft of the
standard.  Is this fact (about the standard-- I'm less concerned about
Watcom's compiler)?  If so, is there some rationale given?

I ask because I am presently designing a system which makes good use
of this feature, and I want to rethink it if the coming standard is
going to make it obsolete...  I am therfore particularly interested to
know if this has been prohibited because there is a "better" technique
available.
--
// Kaelin Colclasure ---------------------------------------------------------
// EMail: kaelin@bridge.com            Mail: Bridge Information Systems, Inc.
// Voice: (314)567-8463                      717 Office Parkway
//   Fax: (314)432-5391                      St. Louis, MO 63141