Re: [PATCH] PR fortran/42546 -- ALLOCATED has 2 mutually exclusive keywords

It looks like a backwards compatibility issue. F95, 13.14.9 ALLOCATED (ARRAY). F2003, 13.7.9 ALLOCATED (ARRAY) or ALLOCATED (SCALAR) Thanks for the quick peek. -- steve On Tue, Aug 06, 2019 at 08:20:28PM +0100, Paul Richard Thomas wrote: > > Who thought of that one in the standard? Uuugh! > >

Re: [PATCH] PR fortran/42546 -- ALLOCATED has 2 mutually exclusive keywords

Hi Steve, Who thought of that one in the standard? Uuugh! The solution looks good to commit - again as far back as you feel inclined to do. Regards Paul On Tue, 6 Aug 2019 at 19:27, Steve Kargl wrote: > > Ping. > > On Thu, Aug 01, 2019 at 02:11:39PM -0700, Steve Kargl wrote: > > The attached

Re: [PATCH] PR fortran/42546 -- ALLOCATED has 2 mutually exclusive keywords

Ping. On Thu, Aug 01, 2019 at 02:11:39PM -0700, Steve Kargl wrote: > The attached patch fixed the issues raised in the > PR fortran/42546. Namely, ALLOCATED has two possible > keywords: ALLOCATE(ARRAY=...) or ALLOCATED(SCALAR=...) > > In Tobias' original patch (attached to the PR), he > tried t

[PATCH] PR fortran/42546 -- ALLOCATED has 2 mutually exclusive keywords

The attached patch fixed the issues raised in the PR fortran/42546. Namely, ALLOCATED has two possible keywords: ALLOCATE(ARRAY=...) or ALLOCATED(SCALAR=...) In Tobias' original patch (attached to the PR), he tried to make both ARRAY and SCALAR options, then in gfc_check_allocated() appropriate