This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug fortran/60913] [OOP] Memory leak with allocatable polymorphic function result (in type-bound operator)
- From: "cmacmackin at gmail dot com" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Wed, 25 Jan 2017 08:11:30 +0000
- Subject: [Bug fortran/60913] [OOP] Memory leak with allocatable polymorphic function result (in type-bound operator)
- Auto-submitted: auto-generated
- References: <bug-60913-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=60913
--- Comment #7 from Chris <cmacmackin at gmail dot com> ---
Damian, can you tell me where in the standard allocatable polymorphic results
are prohibited with pure functions? I've been using them that way in my code,
which compiles without issue using gfortran. I haven't tested it with another
compiler although coincidentally I was planning to do that later today.
I am aware of forall being declared deprecated. The example I posted was just a
shortened version of that used at the start of this report. I don't use forall
in my own code.