https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80046
janus at gcc dot gnu.org changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|WAITING |NEW
--- Comment #2 from janus at gcc dot gnu.org ---
(In reply to Joachim Herb from comment #0)
> Is this an intended behavior?
Well, at least the error on the second procptr assignment is intended behavior.
See PR 56261 for discussion.
The only 'bug' is that gfortran does not reject the first one as well.
> If so, what would be the correct way to handle such pointers?
The correct way would be the one pointed out by Dominique in comment #1, namely
giving 'cloneProc' an explicit interface.
