Hi all,
while working at teams stuff I encountered some issue with the ASSOCIATE
statement:
1. First of all: It does not open its namespace as it is expected to. I.e. the
associate-name (referring to the term as used in F2018 11.1.3.1 R1104) is put
into the parent namespace/scope and not into its
This patch is essentially the one of PR101602, comment 6.
Thus, it has the same issues as that patch:
* LOCAL for derived-type variables with default
initalizers do not work (not initialized)
* LOCAL/LOCAL_INIT for assumed-shape arrays fails
(need some 'malloc'/'free' calls + some more other
Hi all,
the attached patch fixes a rather strange 12/13/14/15 regression.
When walking through the list of procedures in an interface to
find the matching one, the code could remember an inferred type
from a false module procedure within the same interface if and
only if optional arguments were i
On 4/8/25 1:43 PM, Harald Anlauf wrote:
Hi all,
the attached patch fixes a rather strange 12/13/14/15 regression.
When walking through the list of procedures in an interface to
find the matching one, the code could remember an inferred type
from a false module procedure within the same interface
On 4/8/25 10:44 AM, Tobias Burnus wrote:
This patch is essentially the one of PR101602, comment 6.
Thus, it has the same issues as that patch:
* LOCAL for derived-type variables with default
initalizers do not work (not initialized)
* LOCAL/LOCAL_INIT for assumed-shape arrays fails
(need s
