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  1997

COMP-FORTRAN-90 1997

Options

Subscribe or Unsubscribe

Subscribe or Unsubscribe

Log In

Log In

Get Password

Get Password

Subject:

Re: Accessebility within modules ?

From:

[log in to unmask] (Phillip Helbig)

Reply-To:

[log in to unmask]

Date:

Mon, 8 Dec 1997 16:23:59 GMT

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (73 lines)


Monday,  8-DEC-1997 16:46:13.16



> From:	SMTP%"[log in to unmask]"  8-DEC-1997 16:10:53.24
> 
> I want to construct my modules (at least some of them) such that modules
> USE'ed within them are invisible outside the module. I'll illustrate the
> problem with a simple example. We define the modules A and B, where B
> depends on A by USE'association. Something like:
> 
> module A
> .
> .
> end module A
> 
> module B
> use A
> .
> .
> end module B
> 
> The behavior I would like is that when USEing B I only have access to the
> public enteties of B and none of the enteties of A ( private or public ). In
> the case I need something from module A I would have to USE A and it would
> not be sufficient to USE B. 

This is similar to a discussion I had recently, except that I preferred
it the other way around, and was wondering if this behaviour is
platform-independent (it should be according to the standard).  I tend 
to prefer the behaviour like it is, as long as it is not FORBIDDEN to 
access a MODULE doubly (it's not) though I see your point.  If you just 
want a few thing from A, then USE A, ONLY: is what you need (B can still 
USE what it wants of A).  If you want to exclude a few things, then use 
the M&R trick USE A, EXCEPT_THIS = > FOO, EXCEPT_THAT => BAR (and of 
course don't use the variables EXCEPT_THIS and EXCEPT_THAT in your 
code).  However, there are intermediate cases where one must include a 
lot of typing to get the desired effect.

I'm not sure if the exclusion will work if A is USEd through B, although 
it would be nice if it did.  Comments?

It seems a lot of people would like PRIVATE to be the default, to have a 
READONLY attribute for MODULE variables, and to disallow the implicit 
USE (through another module) as you suggested.  At first and even second 
thought, I tend to agree, as I do with the suggestion of having IMPLICIT 
NONE to be the default (at least for free-form source:) (those who don't 
want it, and there might be some arguments which aren't all bad, can 
have a compiler switch or have their editor include the line 
IMPLICIT REAL (A-H), (O-Z), INTEGER (I-N)).

Comments on these four suggestions as to why NOT to do them (I assume 
the reasons TO do them are obvious) and reasons, if any, why it is 
forever to late to change the default behaviour?  


Phillip (donning flame-proof suit:)


--
Phillip Helbig                          Email .......... [log in to unmask]
Nuffield Radio Astronomy Laboratories   Tel. ..... +44 1477 571 321 (ext. 297)
Jodrell Bank                            Fax ................. +44 1477 571 618
Macclesfield                            Telex ................. 36149 JODREL G
UK-Cheshire SK11 9DL                    Web .... http://www.jb.man.ac.uk/~pjh/

My opinions are not necessarily those of NRAL or the University of Manchester.



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

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