Prev: How to control/prevent cast between from complex to real variables
Next: How to pass function names as arguments when function returns an array?
From: Richard Maine on 15 Feb 2010 17:20
Harald Anlauf <anlauf.2008(a)arcor.de> wrote:

> On Feb 15, 10:09 pm, Berfux <ber...(a)gmail.com> wrote:
> > In g95 (with option -Wall) I got two warnings :
> >
> > x = z
> > 1
> > Warning (140): Implicit conversion at (1) may cause precision loss
>
> The warning are correct.

Eh? How so? I can imagine no way in which that would happen for the code
shown. This is a conversion from single precision complex to single
precision real. Those are both the same precision; no way you are going
to get precision loss. Of course, you "lose" the complex part, but that
isn't the same thing as precision. If that's what the message is trying
to imply, it is very misleading.

--
Richard Maine | Good judgment comes from experience;
email: last name at domain . net | experience comes from bad judgment.
domain: summertriangle | -- Mark Twain
 | 
Pages: 1
Prev: How to control/prevent cast between from complex to real variables
Next: How to pass function names as arguments when function returns an array?