Re: [RFC, Fortran, (pr66775)] Allocatable function result

[Dan Nagle]

Hi,

> On Jul 11, 2015, at 04:36 , Andre Vehreschild  wrote:
> 
>> 
>>   "On completion of execution of the function, the value returned
>>is that of its function result. ... If the function result is
>>not a pointer, its value shall be defined by the function."
> 
> Now we can argue whether the "shall be defined" is to be interpreted as "has 
> to
> be" or as "might be". For me - being a non-native English speaker - that 
> "shall"
> is not an obligation but should be interpreted as "commonly the function 
> result
> is to be defined, but there can be exceptions". Now I am curious about how
> native English speakers understand that standard statement.

The standard is written in standardese, not English.

“Shall” is a requirement.  Full stop.

--

Cheers!
Dan Nagle

Re: [Fortran, Patch] First patch for coarray FAILED IMAGES (TS 18508)

[Dan Nagle]

Hi,

The failed images features of gfortran are exciting,
and folks here would like to start testing with their scientific codes.
I’d like to build a new gfortran to support them,
but I must build from a trusted source,
which means from trunk, without custom patches.

Can Alessandro’s patch get a review?

Many thanks!

> On Jun 21, 2016, at 10:59, Alessandro Fanfarillo  
> wrote:
> 
> * PING *
> 
> 2016-06-06 15:05 GMT-06:00 Alessandro Fanfarillo :
>> Dear all,
>> 
>> please find in attachment the first patch (of n) for the FAILED IMAGES
>> capability defined in the coarray TS 18508.
>> The patch adds support for three new intrinsic functions defined in
>> the TS for simulating a failure (fail image), checking an image status
>> (image_status) and getting the list of failed images (failed_images).
>> The patch has been built and regtested on x86_64-pc-linux-gnu.
>> 
>> Ok for trunk?
>> 
>> Alessandro


--

Cheers!
Dan Nagle