public inbox for fortran@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jim Secan <james.secan@gmail.com>
To: Jerry DeLisle <jvdelisle@charter.net>, gfortran <fortran@gcc.gnu.org>
Subject: Re: DEC Extension Support for gcc-4.8.3
Date: Tue, 08 Mar 2016 18:39:00 -0000	[thread overview]
Message-ID: <29BA63D4-E433-4C8A-B4A9-0509453F0A77@gmail.com> (raw)
In-Reply-To: <56DF0FBF.3040605@charter.net>

As an “end user” of this compiler and a five-decades Fortran coder I am happy to see the DEC extensions added to gfortran, particularly the structures framework.  I am, as others suggest, slowly converting old code over to use derived types, but I’d prefer to be spending my time on my day job rather than reinventing wheels.  Some things, like the $ inclusion in variable names and other musty old stuff, are definitely in the “clean it up” hopper.  Others, structures being the main one, also raise old memories (and not fond ones) of the Fortran committee rejecting this de-facto standard in the first place.

Anyway, I welcome the addition of the structures formalism to gfortran.  I don’t see it as a compiler hack as much as helpful extension.

Jim
3222 NE 89th St
Seattle, WA 98115
(206) 430-0109

On Mar 8, 2016, at 9:45 AM, Jerry DeLisle <jvdelisle@charter.net> wrote:

> On 03/07/2016 04:10 PM, W Spector wrote:
>> Tim Prince <n8tm at aol dot com> wrote:
>>> ... 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.
>> 
>> Allowing $ in variable names was an old, old, ('60s/'70s) IBM mainframe
>> extension, and maybe others of the era too.  I first encountered it in 1978 or
>> so. So definitely pre-VAX.
>> 
>> Some dusty brain cells are thinking it may have been also used by some compilers
>> (or pre-processors) to separate statements on a single line. Which of course is
>> now done with semi-colons.
>> 
>> Walter
>> 
> 
> IMHO for some of these things on legacy code, judicious use of editors like sed
> should be used on the source codes and just bring them out of the dark ages.  It
> really is not that hard.  If the code is that important then just do it.
> Hacking compilers out of laziness just does not seem right.
> 
> I am not saying anyone is lazy and do not intend to offend, I fully understand
> what it is like to have over bearing workloads, but we should at least do a
> reality check.
> 
> Regards,
> 
> Jerry

  reply	other threads:[~2016-03-08 18:39 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-08  0:11 W Spector
2016-03-08 17:45 ` Jerry DeLisle
2016-03-08 18:39   ` Jim Secan [this message]
2016-03-09 10:41   ` Jim MacArthur
  -- strict thread matches above, loose matches on Subject: below --
2016-03-08 22:03 W Spector
2016-03-08 18:14 Walter Spector
2016-03-08 18:26 ` Jerry DeLisle
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

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=29BA63D4-E433-4C8A-B4A9-0509453F0A77@gmail.com \
    --to=james.secan@gmail.com \
    --cc=fortran@gcc.gnu.org \
    --cc=jvdelisle@charter.net \
    /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).