IMPURE ELEMENTALs
in [Fortran]
|
From: James Giles on 1 Jul 2008 17:39 I'm in the middle of writing some comments for the 2008 public review, and I'd like some discussion on this one before I submit it. I don't see the value in having IMPURE ELEMENTAL procedures. There are no examples in the draft standard and the only example in the document describing new features can be rewritten without the procedure being ELEMENTAL at all. To be sure, other ways of calling the procedure are possible but they are likely to be more confusing to the reader than non-ELEMENTAL alternatives. -- J. Giles "I conclude that there are two ways of constructing a software design: One way is to make it so simple that there are obviously no deficiencies and the other way is to make it so complicated that there are no obvious deficiencies." -- C. A. R. Hoare "Simplicity is prerequisite for reliability" -- E. W. Dijkstra
From: robert.corbett on 1 Jul 2008 21:47 On Jul 1, 2:39 pm, "James Giles" <jamesgi...(a)worldnet.att.net> wrote: > I'm in the middle of writing some comments for the 2008 > public review, and I'd like some discussion on this one before > I submit it. Thank you for taking time to comment on the Fortran 2008 draft. I hope more people will do the same. Bob Corbett
From: James Giles on 1 Jul 2008 22:13 robert.corbett(a)sun.com wrote: > On Jul 1, 2:39 pm, "James Giles" <jamesgi...(a)worldnet.att.net> wrote: > >> I'm in the middle of writing some comments for the 2008 >> public review, and I'd like some discussion on this one before >> I submit it. > > Thank you for taking time to comment on the > Fortran 2008 draft. I hope more people will do > the same. The time alloted expires Sunday as I recall the announcement. I haven't decided whether to actually send in the comment of this thread. I probably will since no one has yet given a convincing example of a good IMPURE ELEMENTAL. But, I'll give another day or two. I may post some of my other public review comments here as well. I would kind of like to see something that the committee seldom does in the public review: what my high school English teacher used to call "compare and contrast". -- J. Giles "I conclude that there are two ways of constructing a software design: One way is to make it so simple that there are obviously no deficiencies and the other way is to make it so complicated that there are no obvious deficiencies." -- C. A. R. Hoare "Simplicity is prerequisite for reliability" -- E. W. Dijkstra
From: Dan Nagle on 2 Jul 2008 05:47 Hello, On 2008-07-01 22:13:44 -0400, "James Giles" <jamesgiles(a)worldnet.att.net> said: > > The time alloted expires Sunday as I recall the announcement. The time limits were set by ANSI, and had to be exactly 30 days. J3 had no choice. The SUN rep on J3, who volunteered to collect and forward the comments, will certainly take a comment on Monday. (Friday through Sunday is a public holiday weekend here in the USA.) -- Cheers! Dan Nagle
From: robert.corbett on 2 Jul 2008 07:19
On Jul 2, 2:47 am, Dan Nagle <danna...(a)verizon.net> wrote: > The time limits were set by ANSI, and had to be > exactly 30 days. J3 had no choice. Thirty days is a short time to review a draft the size of the Fortran 2008 CD. Nonetheless, in my case having more time would not make a difference. I have already spent more time on the review than my masters like. Bob Corbett |