Dear Paul,
I have tested your patch (with the two patches in pr67429) and got the
following regressions:
FAIL: gfortran.dg/bind_c_usage_12.f03 -O (test for errors, line 33)
FAIL: gfortran.dg/bind_c_usage_12.f03 -O (test for errors, line 51)
FAIL: gfortran.dg/bind_c_usage_12.f03 -O (t
Dear FX and Mikael,
Please hold off on reviewing the patch until I say so. Some rather
trivial looking tidying up before submission has introduced a dozen or
so regressions :-(
Cheers
Paul
On 27 August 2015 at 16:54, FX wrote:
> Hi Paul,
>
> I’ll get to reviewing the patch tonight or tomorrow…
Le 27/08/2015 16:54, FX a écrit :
I think it shouldn’t be too hard to get the ambiguity lifted. We already can do
it for array assignment vs. statement functions, so maybe we could get a hint
from that?
Well, for array assignments, the array is declared before, whereas for
pointer functions,
Hi Paul,
I’ll get to reviewing the patch tonight or tomorrow…
I think it shouldn’t be too hard to get the ambiguity lifted. We already can do
it for array assignment vs. statement functions, so maybe we could get a hint
from that?
touille /tmp $ cat a.f90
integer :: f(2) = 0
integer :: x =
Dear All,
The attached patch more or less implements the assignment of
expressions to the result of a pointer function. To wit:
my_ptr_fcn (arg1, arg2...) = expr
arg1 would usually be the target, pointed to by the function. The
patch parses these statements and resolves them into:
temp_ptr => m
