🚀 go-pugleaf

RetroBBS NetNews Server

Inspired by RockSolid Light RIP Retro Guy

Article View: comp.lang.misc
Article #166

Re: Fortran90 and Arrays

#166
From: Raul Deluth Miller-Rockwell
Date: Mon, 13 Apr 1992 00:42
53 lines
2927 bytes
Stephen P Spackman:
>  How about having NO reserved words?

Easy to implement, though I'm not sure what the benefit is.  If you
want to go even further "out there" you might consider methods to
dynamically alter the parser's word-formation rules -- but again, I
don't see the benefit.  Certainly, it would be strange to find that

  IF (X = 1) THEN PRINT Y;

meant 'compute the set intersection of the sets named ) and THEN, and
store the result under the name ;'.

And it would be even stranger to find that the whole line was a single
identifier.

Stephen P Spackman:
>  |   Part of the reason, of course, is that there isn't enough of a
>  |   type system to resolve overloads.

Me:
>  |I'm not quite sure what this means.

Stephen P Spackman:
>  Just that since there are no static types, and very, very few
>  dynamic ones, it's hard to reuse a symbol: * couldn't be used for
>  set intersection because you can't tell if a vector is intended to
>  be interpreted as a set or not - that isn't recorded anywhere. So
>  operators are in VERY short supply. Which is why there need to be
>  so many squiggles, and why Iverson needs them all for himself :-).

Operators are not in short supply -- or maybe you're using a different
definition of "operator" than Jim Giles?  I could easily define an
operator named FIND_SET_INTERSECTION, for example.

>  |   But it seems really silly to say "these are my letters and
>  |   those are yours" and make it impossible to build
>  |   application-specific notation within the language.
>  |
>  |I haven't a clue what this means.

>  I mean that it is none of the application programmer's business
>  which functions are "built in" to the language, and which comes
>  from a library that the system architect has provided. So there
>  shouldn't be a syntactic distinction - it gets in the way of doing
>  the job.

But, there is no syntactic distinction.  There is a rhematic
distinction (the word formation rules are different), but I just don't
see why this is bad.

-- 
Raul Deluth Miller-Rockwell                   <rockwell@socrates.umd.edu>
Technical Details
Message-ID: <ROCKWELL.92Apr12194228@socrates.umd.edu>
Path: arc1-ca.pugleaf.net!sparky!uunet!haven.umd.edu!socrates!socrates!rockwell
References: <ROCKWELL.92Mar21001252@socrates.umd.edu> <ROCKWELL.92Apr8001532@socrates.umd.edu> <1992Apr8.180420.9294@newshost.lanl.gov> <ROCKWELL.92Apr8164502@socrates.umd.edu> <STEPHEN.92Apr9214055@estragon.uchicago.edu> <ROCKWELL.92Apr10214059@socrates.umd.edu <STEPHEN.92Apr11045523@estragon.uchicago.edu>

Show Full Headers
Complete Article Headers
Newsgroups: comp.lang.misc
Path: arc1-ca.pugleaf.net!sparky!uunet!haven.umd.edu!socrates!socrates!rockwell
From: rockwell@socrates.umd.edu (Raul Deluth Miller-Rockwell)
Subject: Re: Fortran90 and Arrays
In-Reply-To: stephen@estragon.uchicago.edu's message of 11 Apr 92 09:55:17 GMT
Message-ID: <ROCKWELL.92Apr12194228@socrates.umd.edu>
Sender: rockwell@socrates.umd.edu (Raul Deluth Miller-Rockwell)
Organization: Traveller
References: <ROCKWELL.92Mar21001252@socrates.umd.edu>
 <ROCKWELL.92Apr8001532@socrates.umd.edu>
 <1992Apr8.180420.9294@newshost.lanl.gov>
 <ROCKWELL.92Apr8164502@socrates.umd.edu>
 <STEPHEN.92Apr9214055@estragon.uchicago.edu>
 <ROCKWELL.92Apr10214059@socrates.umd.edu
 <STEPHEN.92Apr11045523@estragon.uchicago.edu>
Date: Mon, 13 Apr 1992 00:42:28 GMT
Lines: 53