Re: [Patch, Fortran] Calling type-bound procedures

[Tobias Burnus <burnus at net-b dot de>]

Paul,

Paul Richard Thomas wrote:
> >  TYPE(mytype) :: dummy_arg
> > one needs
> >  CLASS(mytype):: dummy_arg
> >
> > Thinking about it, it makes sense: Unless the procedure is overwritten,
> > the type%inherited_proc() won't work. (I have not checked what happends
> > currently.)
> >     
> I suggest that we continue to allow this temporarily and emit a
> warning.  That way, all the hooks are there and we can correct it as
> soon as..
>   

I agree - I came to a similar conclusion this morning during a meeting. 
I was curious what happens if one calls an inherited TBP and the answer 
the following error message:

<During initialization>
Error: Type mismatch in argument 'this' at (1); passed TYPE(t2) to TYPE(t)

I think that's OK. I believe the current warning is sufficient. My idea 
is to disable the TYPE() support as soon as CLASS is supported, one 
probably should state this in the release notes. (Or does anyone feel 
like we should support it as vendor extension even after CLASS is 
implemented?)

> It is now partially recreated.  Give me a few days and I might be able
> to offer something useful that will at least allow this to work.
>   
That would be great - hopefully, you will have a submittable patch 
before Stage3 - the reviewing can then extend into the early days of Stage3.

> Other than this - OK for me.
>   
Ditto from me. You can commit is (even today), the dump-parse-tree and 
documentation (and maybe GENERIC ;-) can be done later.

Can you update the GFortran#news, Fortran2003 and Fortran2003status wiki 
pages after the check in? (When GCC has entered stage3, I will post a 
patch for the official GCC 4.4 changelog, incorporating all unmentioned 
changes of the GFortran#news wiki page.)

Tobias