------- Additional Comments From enok at lysator dot liu dot se 2005-05-30 13:27 ------- If CHARACTER is replaced by INTEGER the result is the same. Thus, it is not CHARACTER type pointers that causes the problem.
(In reply to comment #6) > *** Bug 21816 has been marked as a duplicate of this bug. *** (In reply to comment #5) > The problem lies with the character pointer in the derived type. Remove the > assignement to null and this example compiles. Try to allocate pd and it > fails > again. Change to to fixed length, it is OK, but bombs out again when you > assign something to it. The mixture of derived types and characters seems to > be toxic! CVS 20041202 > > (In reply to comment #4) > > Further reduced to: > > TYPE n > > CHARACTER, POINTER :: vc => NULL() > > END TYPE n > > TYPE (n), POINTER :: pd > > END > > this is, I believe, indeed valid. Therefor confirmed this time. > > -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=16606
