JiscMail Logo
Email discussion lists for the UK Education and Research communities

Help for COMP-FORTRAN-90 Archives


COMP-FORTRAN-90 Archives

COMP-FORTRAN-90 Archives


COMP-FORTRAN-90@JISCMAIL.AC.UK


View:

Message:

[

First

|

Previous

|

Next

|

Last

]

By Topic:

[

First

|

Previous

|

Next

|

Last

]

By Author:

[

First

|

Previous

|

Next

|

Last

]

Font:

Proportional Font

LISTSERV Archives

LISTSERV Archives

COMP-FORTRAN-90 Home

COMP-FORTRAN-90 Home

COMP-FORTRAN-90  1999

COMP-FORTRAN-90 1999

Options

Subscribe or Unsubscribe

Subscribe or Unsubscribe

Log In

Log In

Get Password

Get Password

Subject:

Re: About nullify and Deallocate,etc.

From:

"James Giles" <[log in to unmask]>

Reply-To:

James Giles

Date:

Thu, 4 Feb 1999 16:53:32 -0700

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (141 lines)

Walt Brainerd <[log in to unmask]> wrote:
...

>The first half of this sentence is a matter of opinion, of course,
>but could you please show us a program that does a tree sort using
>reallocatable arrays (one that is approximately as readable as the
>F program in http://www.imagine1.com/imagine1/ex_tree_sort.html).
>
>>>>
> I no longer consider recursive data structures as
>sufficient reason to spoil the language with pointers (especially since
>all could be emulated efficiently with reallocatable arrays).

I suspect you intended this to be a challenging exercise.  But, with the
exception that REALLOCATE is not yet in the language, the transformation
is almost mechanical in its simplicity.  Instead of the system's heap, you
allocate your tree on a reallocatable array.  Dereferences of your pointers
become indexes into that array.  Assignments or other definitions of your
pointers become integer assignments to the indices.  I leave the amount
by which the array is allocated and/or incremented undefined here in order
to emphasize that it could be a decision made on a case-by-case basis.
In any case, the fact that you call the system's memory manager only once
every amount() times you allocate a new node on the tree means that
this version is probably even faster than the one using pointers.

Note that, in general, you would also have to implement a MY_DEALLOCATE
routine and maintain a free lins within the array.  This is a complication not needed
in this example.

This was written quickly and without a test, but it should at least get the point 
across (transformed directly from imagine1, plus the addition of MY_ALLOCATE
routine):

module tree_sort_module

public :: insert, print_tree, my_allocate

type, public :: node
   integer :: value
   integer :: left, right ! these are "pointers" into 
                          ! an array of type NODE
end type node

integer, public :: number
integer :: inuse  !number of elements in ARRAY in use
type(node), allocatable :: ARRAY(:) ! in F you probably 
                                    ! use the DIMENSION
                                    ! attribute :-(


contains

   recursive subroutine insert (t)

      integer :: t  ! A tree
      integer :: number

      ! If (sub)tree is empty, put number at root
      if (t == 0) then
         call my_allocate (t)
         ARRAY(t) % value = number
         ARRAY(t) % left = 0
         ARRAY(t) % right = 0
      ! Otherwise, insert into correct subtree
      else if (number < ARRAY(t) % value) then
         call insert (ARRAY(t) % left)
      else
         call insert (ARRAY(t) % right)
      end if

   end subroutine insert

   recursive subroutine print_tree (t)
   ! Print tree in infix order

      integer :: t  ! A tree

      if (t /= 0) then
         call print_tree (ARRAY(t) % left)
         print *, ARRAY(t) % value
         call print_tree (ARRAY(t) % right)
      end if

   end subroutine print_tree

   subroutine my_allocate(t)
   ! assign a space for a new element
   ! (REALLOCATE ARRAY if necessary)

      integer :: t  ! A tree
      integer :: ierr

      if (.not. allocated(ARRAY)) then
         ALLOCATE (ARRAY(amount(), stat = ierr)
         if (ierr /= 0) exit
         t = 1
         inuse = 1
      else if (inuse >= size(ARRAY)) then
         REALLOCATE (ARRAY(inuse+amount()), stat = ierr)
         ! if reallocate existed !!!
         if (ierr /= 0) exit
         inuse = inuse + 1
         t = inuse
      else
         inuse = inuse + 1
         t = inuse
      endif

   end subroutine my_allocate

end module tree_sort_module

program tree_sort
! Sorts a file of integers by building a
! tree, sorted in infix order.
! This sort has expected behavior n log n,
! but worst case (input is sorted) n ** 2.

   use tree_sort_module

   integer :: t = 0  ! A tree (initially empty)
   integer :: ios

   do
      read (unit=*, fmt=*, iostat = ios) number
      if (ios < 0) then
         exit
      end if
      call insert (t) ! Put next number in tree
      ! NUMBER is public in the module and is an
      ! implicit argument to INSERT
   end do
   ! Print nodes of tree in infix order
   call print_tree (t)

end program tree_sort



%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%

Top of Message | Previous Page | Permalink

JiscMail Tools


RSS Feeds and Sharing


Advanced Options


Archives

December 2023
February 2023
November 2022
September 2022
February 2022
January 2022
June 2021
November 2020
September 2020
June 2020
May 2020
April 2020
December 2019
October 2019
September 2019
March 2019
February 2019
January 2019
November 2018
October 2018
September 2018
August 2018
July 2018
May 2018
April 2018
March 2018
February 2018
January 2018
December 2017
November 2017
October 2017
September 2017
August 2017
July 2017
June 2017
May 2017
April 2017
March 2017
January 2017
December 2016
November 2016
October 2016
September 2016
August 2016
July 2016
June 2016
May 2016
April 2016
March 2016
February 2016
December 2015
November 2015
October 2015
September 2015
August 2015
June 2015
April 2015
March 2015
January 2015
December 2014
November 2014
October 2014
August 2014
July 2014
May 2014
April 2014
March 2014
February 2014
January 2014
December 2013
November 2013
July 2013
June 2013
May 2013
April 2013
February 2013
January 2013
December 2012
November 2012
October 2012
September 2012
August 2012
July 2012
June 2012
April 2012
March 2012
February 2012
January 2012
December 2011
November 2011
October 2011
September 2011
August 2011
July 2011
June 2011
May 2011
April 2011
March 2011
February 2011
January 2011
December 2010
November 2010
October 2010
August 2010
July 2010
June 2010
March 2010
February 2010
January 2010
December 2009
October 2009
August 2009
July 2009
June 2009
March 2009
February 2009
January 2009
December 2008
November 2008
October 2008
September 2008
August 2008
July 2008
June 2008
May 2008
April 2008
March 2008
February 2008
December 2007
November 2007
October 2007
September 2007
August 2007
July 2007
June 2007
May 2007
April 2007
March 2007
January 2007
2006
2005
2004
2003
2002
2001
2000
1999
1998
1997


JiscMail is a Jisc service.

View our service policies at https://www.jiscmail.ac.uk/policyandsecurity/ and Jisc's privacy policy at https://www.jisc.ac.uk/website/privacy-notice

For help and support help@jisc.ac.uk

Secured by F-Secure Anti-Virus CataList Email List Search Powered by the LISTSERV Email List Manager