[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

20040525: comment on non-standard compliant code in gempak



Keith,

presumably j = -1 * i would be an acceptable combination too
since it avoids the consecutive operators.

So since I have you on the line, we are still stuck at SUNWS5.0
for our X86 environment, while running WS 7.0 for sparc.
Is there any hope of getting the X86 compiler environment up
in line with the sparc platforms?

Steve Chiswell
Unidata User Support


>From: Keith Bierman <address@hidden>
>Organization: Sun Microsystems
>Keywords: 200405252249.i4PMn6tK019690

>This is a multi-part message in MIME format.
>
>--Boundary_(ID_VhLtZ7DNhXexoSqS0l0hXQ)
>Content-type: text/plain; charset=us-ascii; format=flowed
>Content-transfer-encoding: 7BIT
>
>*GEMPAK Source Code distribution, V5.7.2p2
>**imnex2.f
>*lines 138 and 158 (at least). The nonstandard compliant construct is of 
>the form:
>
>    j=i*-1
>
>While many compilers permit the usage (two consequtive operators) , it 
>was never actually conformant with any Fortran standard (I was on the 
>Fortran committee for over a decade; not that makes me uniquely 
>qualified ... but I'm not just a random person off the street either ;>).
>
>adding () around -1 should take care of the Standards violation.
>
>
>-- 
>Keith H. Bierman    address@hidden|
>Sun Microsystems PAE                     | address@hidden
>12 Network Circle UMPK 12-325            | 650-352-4432 voice+fax
>Menlo Park, California  94025            | sun internal 68207
><speaking for myself, not Sun*> Copyright 2004
>
>--Boundary_(ID_VhLtZ7DNhXexoSqS0l0hXQ)
>Content-type: text/html; charset=us-ascii
>Content-transfer-encoding: 7BIT
>
><!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
><html>
><head>
>  <meta http-equiv="Content-Type" content="text/html;charset=ISO-8859-1">
>  <title></title>
></head>
><body text="#000000" bgcolor="#ffffff">
><font class="option"><b>GEMPAK Source Code distribution, V5.7.2p2<br>
></b></font><font class="option"><b>imnex2.f<br>
></b>lines 138 and 158 (at least). The nonstandard compliant construct
>is of the form:<br>
><br>
>&nbsp;&nbsp;&nbsp; j=i*-1<br>
><br>
>While many compilers permit the usage (two consequtive operators) , it
>was never actually conformant with any Fortran standard (I was on the
>Fortran committee for over a decade; not that makes me uniquely
>qualified ... but I'm not just a random person off the street either
>;&gt;).<br>
><br>
>adding () around -1 should take care of the Standards violation.<br>
><br>
><br>
></font><font class="option"></font>
><div class="moz-signature">-- <br>
><meta content="text/html; charset=ISO-8859-1" http-equiv="content-type">
><title>sigtext</title>
><meta content="keith bierman" name="author">
><span style="font-family: monospace;">Keith H.
>Bierman&nbsp;&nbsp;&nbsp; <a class="moz-txt-link-abbreviated" href="mailto:kei
> address@hidden">address@hidden</a>| </span><br
> style="font-family: monospace;">
><span style="font-family: monospace;">Sun Microsystems PAE &nbsp;
>&nbsp; &nbsp; &nbsp; &nbsp;
>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
>| <a class="moz-txt-link-abbreviated" href="mailto:address@hidden";>kbierman@
> acm.org</a></span><br style="font-family: monospace;">
><span style="font-family: monospace;">12 Network Circle UMPK
>12-325 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
>| 650-352-4432 voice+fax </span><br style="font-family: monospace;">
><span style="font-family: monospace;">Menlo Park, California&nbsp;
>94025&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |
>sun internal 68207</span><br style="font-family: monospace;">
><span style="font-family: monospace;">&lt;speaking for myself, not
>Sun*&gt; Copyright 2004</span><br>
></div>
></body>
></html>
>
>--Boundary_(ID_VhLtZ7DNhXexoSqS0l0hXQ)--
>
--
NOTE: All email exchanges with Unidata User Support are recorded in the
Unidata inquiry tracking system and then made publically available
through the web.  If you do not want to have your interactions made
available in this way, you must let us know in each email you send to us.