|
|
Up |
|
|
  |
Author: Dan NagleDan Nagle Date: Aug 19, 2008 17:02
Hello,
J3's response to the public comments
has been posted to J3's web site at
http://www.j3-fortran.org/doc/year/08/08-272.html
html format is used to enable access
to the primary documents as links.
I'm very proud of J3's efforts last week at 185.
9 people in 4.5 days processed about 75 documents.
For each paper, we had to read it, understand it,
analyze it, reckon a response, and then get the words
right to make it happen.
We weren't able to include "large" changes,
but we did include "small" changes where we could.
Where an issue was too difficult, we submitted
an interpretation request to document the issue
for future processing.
--
Cheers!
Dan Nagle
|
| |
|
| | 14 Comments |
|
  |
Author: Ron FordRon Ford Date: Aug 19, 2008 17:23
On Wed, 20 Aug 2008 00:02:27 GMT, Dan Nagle posted:
Wow, Dan, that looks like a mountain of work.
I noticed in J3's reply to FX a misspelling:
Unfortunately, the premise that intrinsic assignement between character
variables of different kind is allowed is wrong. See table 7.10 on page 152
of the draft: "Type conformance for the intrinsic assignment". Character
assignments are only allowed for "the same kind type parameter". J3
believes the mapping between characters of different kind is difficult to
define. Consequently, J3 declines to make this addition.
Maybe this thread could consider corrections, in particular typos.
--
We must respect the other fellow's religion, but only in the sense and to
the extent that we respect his theory that his wife is beautiful and his
children smart. 5
H. L. Mencken
|
| |
|
| | no comments |
|
  |
Author: Dan NagleDan Nagle Date: Aug 19, 2008 17:42
Hello,
On 2008-08-19 20:23:45 -0400, Ron Ford said:
> I noticed in J3's reply to FX a misspelling:
>
> Unfortunately, the premise that intrinsic assignement between character
> variables of different kind is allowed is wrong.
Sorry, no one caught it. :-(
--
Cheers!
Dan Nagle
|
| |
| no comments |
|
  |
Author: Ron FordRon Ford Date: Aug 19, 2008 18:08
On Wed, 20 Aug 2008 00:42:35 GMT, Dan Nagle posted:
> Hello,
>
> On 2008-08-19 20:23:45 -0400, Ron Ford said:
>
>> I noticed in J3's reply to FX a misspelling:
>>
>> Unfortunately, the premise that intrinsic assignement between character
>> variables of different kind is allowed is wrong.
>
> Sorry, no one caught it. :-(
There's others, but no big deal: it's way to much pressure to have to think
and spell at the same time. That's why God created peer review.
The response that *really* caught my eye was to Richard, who shares my
opinion regarding f08. (He didn't even ask to borrow it.)
|
| Show full article (0.78Kb) |
| no comments |
|
  |
Author: nospamnospam Date: Aug 19, 2008 18:22
Dan Nagle verizon.net> wrote:
...
> I'm very proud of J3's efforts last week at 185.
Indeed. Obviously a lot of work there (and handily presented, too; kudos
to whoever did that). On skimming, I find that I disagree with a few
things, to no great surprise, though mostly not major stuff.
I didn't really expect acceptance of my comment, though I felt I should
make it anyway. Probably the one other big thing is about the biggest
single new feature in the draft. I share Bob Corbett's concern about
co-arrays. (Hmm. I haven't studied it, but I wonder if an implementation
might be able to squeek by with allowing only a single image and then
making most of the co-array stuff pretty much collapse into extra rank
of ordinary arrays.)
One somewhat trivial point I noticed. I also disagree with the reply to
Corbett's comment about the multiple models for generic intrinsics
(J32024). The descriptive model for generic intrinsics changed...
|
| Show full article (2.69Kb) |
| no comments |
|
  |
|
|
  |
Author: nospamnospam Date: Aug 19, 2008 19:35
Gary Scott sbcglobal.net> wrote:
> Ron Ford wrote:
>> I noticed in J3's reply to FX a misspelling:
>>
>> Unfortunately, the premise that intrinsic assignement between character
>> variables of different kind is allowed is wrong. See table 7.10 on...
|
| Show full article (1.97Kb) |
| no comments |
|
  |
Author: Gary ScottGary Scott Date: Aug 19, 2008 19:55
Richard Maine wrote:
> Gary Scott sbcglobal.net> wrote:
>
>
>>Ron Ford wrote:
>
>
>>>I noticed in J3's reply to FX a misspelling:
>>>
>>>Unfortunately, the premise that intrinsic assignement between character...
|
| Show full article (2.98Kb) |
| no comments |
|
  |
Author: James GilesJames Giles Date: Aug 19, 2008 20:48
Gary Scott wrote:
...
> [...] Code point translation is well understood, been
> implented in various operating systems and applications for many
> decades. A precise definition of the contents of the code pages isn't
> necessary to describe the general desired behavior. It isn't a
> problem in the mast majority of usages that the mapping isn't
> perfect, that it cant handle situations where the glyphs don't exist
> in one or the other code page. You could even make those cases a one
> for one mapping to the same code point value. Surely there are
> standards in this area that could be referenced.
The problem is that these issues are beyond the scope of the
Fortran standard. I think the committee should just go ahead
with permitting mixed-KIND character operations and use
the "implementation dependent" description. Then in the
section notes they should reference the appropriate other
standards (ASCII, ISO-8859-*, EBCDIC, etc.). Those
other standards are where the appropriate correspondences
are defined.
|
| Show full article (1.36Kb) |
| no comments |
|
  |
|
|
  |
Author: Reinhold BaderReinhold Bader Date: Aug 20, 2008 05:56
Richard Maine schrieb:
[...]
> I didn't really expect acceptance of my comment, though I felt I should
> make it anyway. Probably the one other big thing is about the biggest
> single new feature in the draft. I share Bob Corbett's concern about
> co-arrays. (Hmm. I haven't studied it, but I wonder if an implementation
> might be able to squeek by with allowing only a single image and then
> making most of the co-array stuff pretty much collapse into extra rank
> of ordinary arrays.)
I'm pretty sure such an implementation would be conforming. However there's
a large class of parallel patterns which needs at least two images to run correctly,
and/or without blocking.
[...]
|
| |
| no comments |
|
|
|
|