Re: Derived types and allocatable

Kurt Kallblad <kurt.kallblad@[EMAIL PROTECTED]
> wrote:

> "Gib Bogle" <g.bogle@[EMAIL PROTECTED]
> wrote in message 
> news:481ff61f$1@[EMAIL PROTECTED]
> <snip>
> > do i = 1,2
> >     if (allocated(cell1(i)%cdata)) then
> >         deallocate(cell1(i)%cdata)
> >     endif
> > enddo
> > if (allocated(cell1)) then
> >     deallocate(cell1)
> > endif
> > do i = 1,2
> >     if (allocated(cell2(i)%cdata)) then
> >         write(*,*) 'deallocate cell2(i)%cdata: ',i
> >         deallocate(cell2(i)%cdata)
> >     endif
> > enddo
> > if (allocated(cell2)) then
> >     deallocate(cell2)
> > endif
> >
> > end
> 
> A different questions:
>  Is it necessery to deallocate the components?

No. Some might prefer it as a style, but it is not necessary.

>  I thought it's enough to deallocate cell1 and cell2.

As a general rule, you can assume that (barring compiler bugs),
allocatables cannot leak memory. You can pretty much deduce the details
from that. If the components weren't automatically deallocated for you,
then forgetting to deallocate them would leak memory. Therefore, you can
deduce that the components will be dealocated for you. The deduction
would be correct.

-- 
Richard Maine                    | Good judgement comes from experience;
email: last name at domain . net | experience comes from bad judgement.
domain: summertriangle           |  -- Mark Twain