https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78661
--- Comment #16 from paul.richard.thomas at gmail dot com <paul.richard.thomas at gmail dot com> --- Dear Janus, What troubles me is that most times I have used namelist, it has been primarily for input to codes; especially where there is a default set of initial conditions and a subset is changed for each run. I suppose that one would have to set up the namelist or the input stream to determine what the dynamic type is, have the code allocate the variable to that type and then do the input. Namelist output is, of course, rather more obvious. Best of all would be that namelist incorporated constructors :-) I see no reason to require that both input and output be present. Cheers Paul On 17 December 2016 at 19:07, janus at gcc dot gnu.org <gcc-bugzi...@gcc.gnu.org> wrote: > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78661 > > --- Comment #14 from janus at gcc dot gnu.org --- > (In reply to paul.richard.tho...@gmail.com from comment #13) >> Why do you think that both input and output is required? > > Don't know. My intuitive reaction was that comment 5 should be valid, but I > haven't looked in the standard. If it is valid, we probably need to move the > check, which currently triggers on the namelist declaration, regardless of > whether it's actually used in any input or output statements. > > >> How is namelist supposed to work with classes? Just with the declared type? > > As with 'normal' I/O, I'd say, i.e. calling the DTIO procedure according to > the > dynamic type (not the declared type!). At least that's what my patch does ... > > -- > You are receiving this mail because: > You are on the CC list for the bug.
