Xref:	news2.mv.net comp.os.msdos.djgpp:7681
From:	weiqigao AT crl DOT com (Weiqi Gao)
Newsgroups:	comp.os.msdos.djgpp
Subject:	Re: COMPLEX
Date:	Tue, 20 Aug 1996 13:40:19 GMT
Organization:	CRL Dialup Internet Access
Lines:	25
Message-ID:	<4vcf8k$456@nntp.crl.com>
References:	<Pine DOT LNX DOT 3 DOT 91 DOT 960820113557 DOT 1284B-100000 AT aditya DOT unigoa DOT ernet DOT in>
NNTP-Posting-Host:	crl10.crl.com
To:	djgpp AT delorie DOT com
DJ-Gateway:	from newsgroup comp.os.msdos.djgpp

Gurunandan R Bhat <grbhat AT unigoa DOT ernet DOT in> wrote:

>i can suggest two problems right away:

>(1) you must #include<_complex.h> not complex.h. the underscore is 
>there to compensate for the fact that the correct header file is 
>Complex.h and MS-DO$ is not case sensitive. i think it is mentioned in 
>the FAQ (sorry eli ;)

>(2) complex numbers are declared with a uppercase C like so:

>Complex c Complex(1.1, 2.2)

I think <complex> is the ANSI draft standard header.  The standard
also allows <complex.h> for compatibility reasons.  One is a wrapper
around the other, and the contents are the STL "complex" definitions.

The old <Complex.h> (<_complex.h> in DOS) is non-ANSI standard by now,
and DJGPP's <_complex.h> merely #include-s <complex> and typedefs
Complex as complex<double>.

--
Weiqi Gao
weiqigao AT crl DOT com

- Raw text -