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  April 2011

COMP-FORTRAN-90 April 2011

Options

Subscribe or Unsubscribe

Subscribe or Unsubscribe

Log In

Log In

Get Password

Get Password

Subject:

Re: polymorphic pointer dummy and Note 12.27

From:

Van Snyder <[log in to unmask]>

Reply-To:

Fortran 90 List <[log in to unmask]>

Date:

Wed, 27 Apr 2011 15:43:28 -0700

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (63 lines)

On Wed, 2011-04-27 at 14:17 -0700, Neil N. Carlson wrote:
> On Wed, 2011-04-27 at 13:59 -0700, Van Snyder wrote:
> > Your actual argument is a pointer, so it has the TARGET attribute.
> > Without the POINTER attribute, it needs the TARGET attribute if you
> > expect any associations with the dummy argument (and thereby with the
> > actual argument) to persist after INIT returns.  I assume you want the
> > association this%x => x to persist.
> > 
> > Just change the dummy argument  X in INIT from POINTER to TARGET and
> > your code works (at least in Intel (R) Fortran 12.0-1230).  If the dummy
> > argument is neither a pointer nor allocatable, the actual argument
> > doesn't have to be polymorphic.
> 
> Right.  But for the association to persist the actual must either be a
> pointer or have the target attribute as you noted, however this isn't
> required and so this interface is easily misused and the compiler isn't
> going to catch it.  That's why I shy away from this.

If the assignment in INIT were performed inline, the target would be
required to have either the TARGET or POINTER attribute, and the
compiler would be required detect this.  It might not detect the case
where the pointer assignment occurs in a subroutine -- because it's not
required.  If the actual argument has neither the POINTER nor TARGET
attribute, and there is a pointer associated with it somewhere, the
compiler won't know that there is a potential aliasing problem.  For
example, it might keep the target (or pieces of it) in a register, and
not realize that changes might have occurred by way of a pointer
associated with it.  So, in either case, your target better have either
the POINTER or TARGET attribute.

Pay your money and take your choice:  Give the POINTER attribute to the
actual argument (which requires the same declared type for actual and
dummy arguments), or give the TARGET attribute to the actual argument.

12.5.2.5p1-2 in the F08 standard could be relaxed a tiny bit so as not
to apply to pointer dummy arguments with the INTENT(IN) attribute.  In
that case, the scenario described in Note 12.27 can't happen.

> > > (3) Section C.9.4 (section 1, case (ii)) suggests making the dummy a
> > > pointer with INTENT(IN) and the actual a non-pointer with the target
> > > attribute (compiler enforced?)  The compiler I'm using won't swallow
> > > this.  Either I've misunderstood this, or this feature (new to 2008 I
> > > believe) isn't implement yet.
> 
> Did I understand C.9.4 correctly?  Can the dummy be an INTENT(IN)
> pointer and the actual a non-pointer with a compiler-enforced target
> attribute?  The answer is somewhat moot, since I this is F2008 and
> there's not much support for that yet.

First, C.9.4 is informative, not normative.  But, yes, Fortran 2008 does
allow an intent(in) pointer dummy argument to correspond to a
non-pointer actual argument, provided the actual argument has the TARGET
attribute.  The compiler might or might not enforce the requirement for
the actual argument to have the TARGET attribute. 12.5.2.7p2 in the F08
standard is an ordinary paragraph, not a constraint.  As such, it is
requirement on the program, not the processor.  It could conceivably be
a constraint, since explicit interface is required if a procedure has a
dummy argument with the POINTER attribute (12.4.2.2p1(2)(a)) -- but it
isn't a constraint.

> -Neil
> 

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