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  2006

COMP-FORTRAN-90 2006

Options

Subscribe or Unsubscribe

Subscribe or Unsubscribe

Log In

Log In

Get Password

Get Password

Subject:

Re: Multiple use association and renaming

From:

Malcolm Cohen <[log in to unmask]>

Reply-To:

Fortran 90 List <[log in to unmask]>

Date:

Tue, 1 Aug 2006 15:40:45 +0900

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (98 lines)

Martin Dix said:
> Please consider the following example
> 
> module mod1
>    integer :: n=1
> end module mod1
> module mod2
>    use mod1
>    integer :: m=2
> end module mod2
> 
> program usetest
>    use mod1, nx => n
>    use mod2, nx => n
>    integer :: n = 3
>    print*, nx, m, n
> end program usetest
> 
> In the main program n is accessible by use association from both modules 
> mod1 and mod2 and conflicts with the local variable. Renaming these with 
> something like
>    use mod1, n1 => n
>    use mod2, n2 => n
> is ok, but what about using the same name as in the example?

Seems ok.

> Two compilers I use accept this and one says it's an error. I've read 
> section 11.2.1 of the F2003 draft standard and I'm not really any the 
> wiser as to whether this is legal or not. It says that two or more 
> accessible entities may not have the same name, but are these really 
> different accessible entities or not?

What do you mean "these"?  There is only one entity being accessed under
the name NX, and that is the entity N declared in the module MOD1.

You've accessed it twice, once directly and the other via MOD2, but it
is certainly the same entity you are accessing.

A very early F90 interpretation addressed this issue (with a more
complicated example):
--------------------------------------------------------------------------------

NUMBER: 000017
TITLE: Creation of entities by local names in rename-list
KEYWORDS: local name, use renaming
DEFECT TYPE: Interpretation
STATUS: Published

QUESTION: Does a local-name on a rename-list create a new data-entity?  For
example, is the local name Q a new data entity or is Q a rename of the entity P
in the following example?

          MODULE UTIL
            PUBLIC P
            CONTAINS
                 SUBROUTINE P
                 END
          END MODULE UTIL

          MODULE MID1
            USE UTIL, Q=>P    ! Is Q a new data entity or merely a
                              ! renaming of P?
            PUBLIC Q
          END MODULE MID1

          MODULE MID2
            USE UTIL, Q=>P    ! Another renaming of the same entity P?
            PUBLIC Q
          END MODULE MID2

          SUBROUTINE ENDUSER
            USE MID1
            USE MID2
            CALL Q                 ! Is this legal? Does it refer to P?
          END SUBROUTINE ENDUSER

ANSWER: Multiple renames of the same <use-name> do not constitute separate
entities.  Subsequent appearances of the <local-name> refer to the single
entity.  In the example, Q does not create a new entity.  Thus "CALL Q" in the
subroutine is legal.

Discussion: In section 11.3.2 [158:15-16], the standard states that a local name
in the rename list is a "local name for the entity" which is intended to mean
that a new entity is not created.

EDITS:   None.
SUBMITTED BY: E. A. Johnson, 119-EAJ-1 (119.057)
HISTORY: 120-LF-1 (120.089)
         077, ui 18 (jw note)
         92-296 m123 Response proposed, approved by unanimous consent
         N881 WG5 approval
--------------------------------------------------------------------------------

Cheers,
-- 
........................Malcolm Cohen ([log in to unmask]), Nihon NAG, Tokyo.

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