https://gcc.gnu.org/bugzilla/show_bug.cgi?id=48298
--- Comment #11 from Damian Rouson <damian at sourceryinstitute dot org> --- Thanks for the quick response. In recent times, I’ve had the impression that it’s harder to find developers than to find money (not that it’s all that easy to find money). I’ve attempted to fund gfortran development at least twice — once successfully and once unsuccessfully. Damian On Oct 2, 2014, at 10:15 PM, kargl at gcc dot gnu.org <gcc-bugzi...@gcc.gnu.org> wrote: > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=48298 > > kargl at gcc dot gnu.org changed: > > What |Removed |Added > ---------------------------------------------------------------------------- > CC| |kargl at gcc dot gnu.org > > --- Comment #10 from kargl at gcc dot gnu.org --- > (In reply to Damian Rouson from comment #9) >> Oh boy. I'm guessing that's an indication that there won't be any movement >> on this anytime soon. It seems this is one of only two major features >> missing for full Fortran 2003 compliance -- the other being derived type >> parameters. One of the Fortran committee members recently suggested that >> derived type parameters be deprecated. I wonder if the same is true of >> derived type I/O. If the leading open-source Fortran compiler already >> supports some features of Fortran 2008 and Fortran 2015 but has major >> features of Fortran 2003 missing a decade after the publication of the >> standard, maybe that's a sign that the feature should be removed from the >> language. Thoughts? > > It's a sign that those who contribute code, do it for free > and when they have time. No one or entity has stepped forward > to implement DTIO or provide sufficient funding. Cray pointers > got implemented because someone at LBNL hired a summer intern. > ISO C binding got done because someone at Argonne funded a > graduate student/intern. Almost all of my contributions came > about because I needed the feature to work. I don't use or > need DTIO, so it's well down my list of things to hack on. > > -- > You are receiving this mail because: > You are on the CC list for the bug.
