public inbox for fortran@gcc.gnu.org
 help / color / mirror / Atom feed
From: Tim Prince <n8tm@aol.com>
To: fortran@gcc.gnu.org
Subject: Re: DEC Extension Support for gcc-4.8.3
Date: Sun, 06 Mar 2016 13:17:00 -0000	[thread overview]
Message-ID: <56DC2DDC.4020807@aol.com> (raw)
In-Reply-To: <20160306000915.GA15619@nbbrfq>

On 3/5/2016 7:09 PM, Bernhard Reutner-Fischer wrote:
> On Sat, Mar 05, 2016 at 05:37:37PM -0500, Fritz Reese wrote:
>> On Sat, Mar 5, 2016 at 5:08 PM, Bernhard Reutner-Fischer
>> <rep.dot.nop@gmail.com> wrote:
>>>
>>> If you happen to have a DEC Compiler lying around, I'd be interested in how they handle implicit $
>>>
>>> See post scriptum in
>>> https://gcc.gnu.org/ml/fortran/2007-01/msg00060.html
>>
>> It seems ifort treats a leading '$' implicitly as an integer.
>
> Supposedly setting the default type works too with ifort.
>
> I was curious about the behaviour of the DEC compiler, though.
>
> cheers,
>
I have a running copy of CVF from 15 years ago, in case you have a test 
case in mind.
I thought the purpose of permitting '$' was to support VMS system 
function calls, so implicit integer may make sense.  Such programs 
evidently won't be portable even if you reconcile this bit.

-- 
Tim Prince

  reply	other threads:[~2016-03-06 13:17 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-04 16:19 Fritz Reese
2016-03-05 22:08 ` Bernhard Reutner-Fischer
2016-03-05 22:37   ` Fritz Reese
2016-03-06  0:09     ` Bernhard Reutner-Fischer
2016-03-06 13:17       ` Tim Prince [this message]
2016-03-08  0:11 W Spector
2016-03-08 17:45 ` Jerry DeLisle
2016-03-08 18:39   ` Jim Secan
2016-03-09 10:41   ` Jim MacArthur
2016-03-08 18:14 Walter Spector
2016-03-08 18:26 ` Jerry DeLisle
2016-03-08 22:03 W Spector

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=56DC2DDC.4020807@aol.com \
    --to=n8tm@aol.com \
    --cc=fortran@gcc.gnu.org \
    --cc=tprince@computer.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).