From: Mikael Morin <morin-mikael@orange.fr>
To: Harald Anlauf <anlauf@gmx.de>, sgk@troutmask.apl.washington.edu
Cc: fortran <fortran@gcc.gnu.org>, gcc-patches <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH, v3] Fortran: improve array component description in runtime error message [PR30802]
Date: Thu, 21 Mar 2024 14:07:16 +0100 [thread overview]
Message-ID: <6e2444f2-ae34-4482-87fd-b924d0f6811b@orange.fr> (raw)
In-Reply-To: <8dd61d1e-a5ed-4305-b483-e845734e8a4d@gmx.de>
Le 20/03/2024 à 21:24, Harald Anlauf a écrit :
> Hi Mikael, all,
>
> here's now the third version of the patch that implements the following
> scheme:
>
> On 3/15/24 20:29, Mikael Morin wrote:
>> Le 15/03/2024 à 18:26, Harald Anlauf a écrit :
>>> OK, that sounds interesting. To clarify the options:
>>>
>>> - for ordinary array x it would stay 'x'
>>>
>>> - when z is a DT scalar, and z%x is the array in question, use 'z%x'
>>> (here z...%x would look strange to me)
>>>
>> Yes, the ellipsis would look strange to me as well.
>>
>>> - when z is a DT array, and x some component further down, 'z...%x'
>>>
>> This case also applies when z is a DT scalar and x is more than one
>> level deep.
>>
>>> I would rather not make the error message text vary too much to avoid
>>> to run into issues with translation. Would it be fine with you to have
>>>
>>> ... dimension 1 of array 'z...%x' above array bound ...
>>>
>>> only?
>>>
>> OK, let's drop "component".
>>
>>> Anything else?
>>>
>> No, I think you covered everything.
>
> I've created a new helper function that centralizes the generation of
> the abbreviated name of the array (component) and use it to simplify
> related code in multiple places. If we change our mind how a bounds
> violation error message should look like, it will be easier to adjust
> in the future.
>
> Is this OK for 14-mainline?
>
Yes, thanks.
> Thanks,
> Harald
>
>
prev parent reply other threads:[~2024-03-21 13:07 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-24 21:39 [PATCH] Fortran: use name of array component " Harald Anlauf
2024-01-28 11:39 ` Mikael Morin
2024-01-28 19:56 ` Harald Anlauf
2024-01-28 21:43 ` Steve Kargl
2024-01-29 6:51 ` rep.dot.nop
2024-01-29 17:25 ` Harald Anlauf
2024-01-29 20:50 ` Harald Anlauf
2024-01-30 10:38 ` Mikael Morin
2024-01-30 10:46 ` Mikael Morin
2024-03-10 21:31 ` [PATCH, v2] " Harald Anlauf
2024-03-15 16:31 ` Mikael Morin
2024-03-15 17:26 ` Harald Anlauf
2024-03-15 19:29 ` Mikael Morin
2024-03-20 20:24 ` [PATCH, v3] Fortran: improve array component description " Harald Anlauf
2024-03-21 13:07 ` Mikael Morin [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=6e2444f2-ae34-4482-87fd-b924d0f6811b@orange.fr \
--to=morin-mikael@orange.fr \
--cc=anlauf@gmx.de \
--cc=fortran@gcc.gnu.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=sgk@troutmask.apl.washington.edu \
/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).