From: Jerry DeLisle <jvdelisle@verizon.net>
To: Tobias Burnus <burnus@net-b.de>
Cc: gfortran list <fortran@gcc.gnu.org>,
gcc patches <gcc-patches@gcc.gnu.org>
Subject: Re: [patch, fortran] PR41075 Add unlimited format item [F2008]
Date: Mon, 17 Aug 2009 16:14:00 -0000 [thread overview]
Message-ID: <4A896E47.4030708@verizon.net> (raw)
In-Reply-To: <4A89063E.5030603@net-b.de>
On 08/17/2009 12:26 AM, Tobias Burnus wrote:
> On 08/17/2009 05:49 AM, Jerry DeLisle wrote:
>> The attached patch adds the unlimited format feature '*' to gfortran.
>> [...]
>> The feature allows some handy input/output for example when an array
>> size is not know until run time. When used in conjunction with the g0
>> edit descriptor, you can read/write just about anything all chunk-ed
>> together. I can see its usefulness for data serialization.
>
> It is also useful to write comma-separated values.
>
>> I have also attached a simple test case. I should mention that right
>> now I do not check for nested '*' in a format string. I think it may
>> be meaningless because you can never exhaust one to allow the other to
>> take effect. We probably want to think about that and I have not
>> studied the F2008 standard in closer detail to see if there is indeed
>> a constraint defined.
> I could not find any constraint; printing an error is probably wrong,
> but one could print a warning, if one wants to.
>
>> Finally, of lesser import, I have modified several error checks to use
>> the %L feature to give some better error loci.
> Great! I think error loci were a weak point of gfortran.
>
>> Disallowing exponent width with D format specifier may be
>> controversial, though correct.
> How about just rejecting it for -std=f* ? I just tried the D edit
> descriptor with g95 -std=f90 -Wall, NAG f95, ifort, openf95 and sunf95:
> None of them rejected it (or warned about it) - not even the very picky
> NAG f95 compiler. Looking at my real-world code, I also found some
> usage of "D".
>
Committed without the D changes. Will do that part separately.
Thanks,
Jerry
prev parent reply other threads:[~2009-08-17 14:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-17 7:15 Jerry DeLisle
2009-08-17 9:15 ` Tobias Burnus
2009-08-17 16:14 ` Jerry DeLisle [this message]
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=4A896E47.4030708@verizon.net \
--to=jvdelisle@verizon.net \
--cc=burnus@net-b.de \
--cc=fortran@gcc.gnu.org \
--cc=gcc-patches@gcc.gnu.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).