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  2003

COMP-FORTRAN-90 2003

Options

Subscribe or Unsubscribe

Subscribe or Unsubscribe

Log In

Log In

Get Password

Get Password

Subject:

Re: Derived types and pointers

From:

Alistair Mills <[log in to unmask]>

Reply-To:

Fortran 90 List <[log in to unmask]>

Date:

Mon, 31 Mar 2003 22:10:57 +0100

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (194 lines)

Paul

I have had a look at the example kindly supplied by Mike and added a few
enhancements to that you can assign a vector or a scalar to the derived
type.  If you add enough code you can make it behave like a native part of
the language!

Good luck.

Alistair

Here is my re-work of Mike's code:

module d

   IMPLICIT NONE

   ! Define pointer_vector type

   TYPE pointer_vector
      INTEGER, POINTER, DIMENSION(:) :: vect
   END TYPE pointer_vector

   interface assignment(=)
      module procedure ass, ass1, ass2
   end interface

   contains

   subroutine ass(a1, a2)
   type(pointer_vector), intent(out) :: a1
   type(pointer_vector), intent(in)  :: a2
   a1%vect = a2%vect
   end subroutine ass

   subroutine ass1(a1, a2)
   type(pointer_vector),  intent(out) :: a1
   integer, dimension(:), intent(in)  :: a2
   a1%vect = a2
   end subroutine ass1

   subroutine ass2(a1, a2)
   type(pointer_vector), intent(out) :: a1
   integer,              intent(in)  :: a2
   a1%vect = a2
   end subroutine ass2

end module d

PROGRAM test_pointer_vector_prog

use d

IMPLICIT NONE

   INTEGER, DIMENSION(8), TARGET :: target_array
   TYPE(pointer_vector)          :: p_vect1
   TYPE(pointer_vector)          :: p_vect2
   integer                       :: i

   ! Initialise the target

   target_array=(/ (i*10, i=1, size(target_array)) /)

   ! p_vect1%vect points to a section of target array

   p_vect1%vect => target_array(2:size(target_array)-1) 

   ! Allocate p_vect2%vect so that it is the same size as p_vect1%vect

   ALLOCATE(p_vect2%vect(SIZE(p_vect1%vect)))

   ! Set p_vect2%vect

   p_vect2%vect(:) = (/ (i, i=1, size(p_vect2%vect)) /)

   p_vect2 = (/ (i, i=1, size(p_vect2%vect)) /)

   ! Then, do either statement A:
   ! p_vect1%vect=p_vect2%vect
   ! ...or statement B:
   p_vect1=p_vect2

   !
   ! or with some more definitions, you can do other interesting things like
   !

   p_vect1 = (/ (i, i=1, size(p_vect1%vect)) /) ! assign a vector to the
derived type
   PRINT 100, 'p_vect1%vect:',p_vect1%vect

   p_vect1 = 66 ! assign a scalar to the derived type
   PRINT 100, 'p_vect1%vect:',p_vect1%vect

   ! Check what has happened to the target array

   PRINT 100, 'target_array:........',target_array

   100 format(a, t25, 50I5)

END PROGRAM test_pointer_vector_prog


-----Original Message-----
From: Fortran 90 List [mailto:[log in to unmask]] On Behalf Of
Michael Metcalf
Sent: 31 March 2003 19:21
To: [log in to unmask]
Subject: Re: Derived types and pointers


>
> Could someone explain why there is a difference in the effect on the
target of
> statements A and B please? I expected that equating the derived types 
> in statement B would involve equating the components of the derived 
> types,
and
> hence be equivalent to statement A, but it must be more subtle than 
> that.

It is. Statement B is a copy between 2 objects of the same derived data
type. The rule is that non-pointer components have their values copied from
the RHS to the LHS, whereas, as here, pointer components undergo a pointer
assignment: whatever the RHS is pointing at is now pointed at also by the
LHS (see also "Fortran 90/95 Explained", Section 3.12).

>
> Also, is it possible to write an INTERFACE ASSIGNMENT(=) operator for 
> the pointer_vector type that equates the components as statement A 
> does, so
that
> statement B has the same effect as A on the target?

Yes. Attached below. It replaces the implicit pointer assignment by an
ordinary assignment.

Hope that helps,

Mike Metcalf


module d

   IMPLICIT NONE

   ! Define pointer_vector type
   TYPE pointer_vector
      INTEGER, POINTER, DIMENSION(:) :: vect
   END TYPE pointer_vector
   interface assignment(=)
      module procedure ass
   end interface
   contains
   subroutine ass(a1, a2)
      type(pointer_vector), intent(out) :: a1
   type(pointer_vector), intent(in) :: a2
      a1%vect = a2%vect
   end subroutine ass
end module d

PROGRAM test_pointer_vector_prog
use d
IMPLICIT NONE

   INTEGER, DIMENSION(5), TARGET :: target_array
   TYPE(pointer_vector) :: p_vect1
   TYPE(pointer_vector) :: p_vect2

   ! Initialise the target
   target_array=0

   ! p_vect1%vect points to a section of target array
   p_vect1%vect => target_array(2:4)

   ! Allocate p_vect2%vect so that it is the same size as p_vect1%vect
   ALLOCATE(p_vect2%vect(SIZE(p_vect1%vect)))
   ! Set p_vect2%vect
   p_vect2%vect=1

   ! Then, do either statement A:
   !p_vect1%vect=p_vect2%vect

   ! ...or statement B:
   p_vect1=p_vect2

   ! Check what has happened to p_vect1%vect
   PRINT '(A,5I2)',' p_vect%vect:   ',p_vect1%vect

   ! Check what has happened to the target array
   PRINT '(A,5I2)','target_array: ',target_array

END PROGRAM test_pointer_vector_prog

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