public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
* [PATCH, WWW-DOCS] Deprecate non-standard hexadecimal BOZ constants
@ 2020-01-15 15:05 Mark Eggleston
  0 siblings, 0 replies; 3+ messages in thread
From: Mark Eggleston @ 2020-01-15 15:05 UTC (permalink / raw)
  To: gcc-patches, fortran, Steve Kargl, pinskia

Add a note the the Fortran changes to the effect that non-standard BOZ 
constants are deprecated.

Is the wording OK?

-- 
https://www.codethink.co.uk/privacy.html

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: [PATCH, WWW-DOCS] Deprecate non-standard hexadecimal BOZ constants.
  2020-01-15 15:20 Mark Eggleston
@ 2020-01-15 17:04 ` Tobias Burnus
  0 siblings, 0 replies; 3+ messages in thread
From: Tobias Burnus @ 2020-01-15 17:04 UTC (permalink / raw)
  To: Mark Eggleston, gcc-patches, fortran, Steve Kargl, pinskia

Hi Mark,

it is more than just 'X' – also B/O/Z when used as postfix ('AB'Z) are 
nonstandard as in general the use outside DATA and a handful of 
intrinsic functions. For instance,  print *, Z'ABC'  is also nonstandard 
and affected by -fallow-invalid-boz. (GCC < 10 silently accepted the 
latter.)

I also come up with a gcc-10/changes.html wording; however, I am sure 
that my wording should be tweaked as well.

See https://gcc.gnu.org/ml/gcc-patches/2020-01/msg00896.html — I 
additionally also modified the diagnostic and the documentation; 
hopefully, in a sensible way.

Thanks,

Tobias

On 1/15/20 3:50 PM, Mark Eggleston wrote:
> Add a note the the Fortran changes to the effect that non-standard BOZ 
> constants are deprecated.
>
> Is the wording OK?
>
> second attempt this time with attachment!
>
> -- 
> https://www.codethink.co.uk/privacy.html
>
>
> deprecated.diff
>
> diff --git a/htdocs/gcc-10/changes.html b/htdocs/gcc-10/changes.html
> index 8e72bd4..3e73cea 100644
> --- a/htdocs/gcc-10/changes.html
> +++ b/htdocs/gcc-10/changes.html
> @@ -269,6 +269,11 @@ a work-in-progress.</p>
>       can be used to disable inline argument packing.
>     </li>
>     <li>
> +    Deprecating non-standard hexadecimal BOZ constants. Hexadecimal BOZ using the
> +    'X' prefix or suffix e.g. X'ABC' or 'ABC'X will only be allowed with the
> +    -fallow-invalid-boz option.
> +  <li>
> +  <li>
>       Legacy extensions:
>       <ul>
>         <li>

^ permalink raw reply	[flat|nested] 3+ messages in thread

* [PATCH, WWW-DOCS] Deprecate non-standard hexadecimal BOZ constants.
@ 2020-01-15 15:20 Mark Eggleston
  2020-01-15 17:04 ` Tobias Burnus
  0 siblings, 1 reply; 3+ messages in thread
From: Mark Eggleston @ 2020-01-15 15:20 UTC (permalink / raw)
  To: gcc-patches, fortran, Steve Kargl, pinskia

[-- Attachment #1: Type: text/plain, Size: 208 bytes --]

Add a note the the Fortran changes to the effect that non-standard BOZ 
constants are deprecated.

Is the wording OK?

second attempt this time with attachment!

-- 
https://www.codethink.co.uk/privacy.html


[-- Attachment #2: deprecated.diff --]
[-- Type: text/x-patch, Size: 537 bytes --]

diff --git a/htdocs/gcc-10/changes.html b/htdocs/gcc-10/changes.html
index 8e72bd4..3e73cea 100644
--- a/htdocs/gcc-10/changes.html
+++ b/htdocs/gcc-10/changes.html
@@ -269,6 +269,11 @@ a work-in-progress.</p>
     can be used to disable inline argument packing.
   </li>
   <li>
+    Deprecating non-standard hexadecimal BOZ constants. Hexadecimal BOZ using the
+    'X' prefix or suffix e.g. X'ABC' or 'ABC'X will only be allowed with the
+    -fallow-invalid-boz option.
+  <li> 
+  <li>
     Legacy extensions:
     <ul>
       <li>

^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2020-01-15 16:46 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2020-01-15 15:05 [PATCH, WWW-DOCS] Deprecate non-standard hexadecimal BOZ constants Mark Eggleston
2020-01-15 15:20 Mark Eggleston
2020-01-15 17:04 ` Tobias Burnus

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).