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  2004

COMP-FORTRAN-90 2004

Options

Subscribe or Unsubscribe

Subscribe or Unsubscribe

Log In

Log In

Get Password

Get Password

Subject:

Re: Deallocating array pointers

From:

Richard E Maine <[log in to unmask]>

Reply-To:

Fortran 90 List <[log in to unmask]>

Date:

Mon, 15 Nov 2004 12:18:55 -0800

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (59 lines)

On Nov 15, 2004, at 11:52 AM, Aleksandar Donev wrote:

> To finally answer a thread started long ago, J3 passed an interp at its
> last meeting...

Please note that J3 passing an interp does *NOT* constitute a final
answer.  That is but one step of interp processing.  Although it is a
very important step, it is rather far from a final one.  It isn't even
the final J3 step. Interps passed at a meeting must also pass a
subsequent letter ballot.  It is not unusual for interps that passed at
a meeting to fail a subsequent letter ballot after there has been more
time for reflection and for issues to be raised.  After passing the J3
letter ballot, the interp must then go to WG5 and pass there also.  It
also has happened quite a few times that interps fail at that stage.

You presumably know this, Aleksandar, but there are presumably readers
of this list that do not.  Therefore, I thought it important to clarify
the usage of "final".

> J3's ANSWER:
>
> Yes, this is allowed, since "whole" means that b is
> ASSOCIATED with all elements of an array that was ALLOCATEd.
> In the given example, ASSOCIATED(a,b) is .TRUE., therefore either
> a or b can be used to DEALLOCATE the memory.

Allow me to note that the 2 sentences in the answer seem to contradict
each other (which is among the kinds of reasons that sometimes cause
interps that pass at a meeting to be rejected later).  The first
sentence talks about all the elements being associated.  The second
sentence talks about the result of the ASSOCIATED intrinsic. The
wording seems to imply that these 2 conditions are the same, which is
incorrect (as was elaborated in one of the early f90 interps from long
ago).  This leaves it unclear in at least my mind which of the 2
different conditions is actually intended.

For those who might wonder how all the elements could be associated
without the associated intrinsic returning .true., consider the
situation after

  b => a(10:1:-1)

There is a 1-to-1 mapping between the elements of a and b.  Every
element of "a" is associated with an element of b and vise versa.
However, associated(a,b) returns .false.. If J3 forgot about that
distinction, then I predict that the interp will need reconsideration.
In any event, I'd think that the wording of the answer ought to be more
precise in order to avoid an interp request about how to interpret the
interpretation.

I'll not try to reopen argument about which answer should be given.
I'll just suggest that, whatever answer is given, it ought to be
written self-consistently.

--
Richard Maine                |  Good judgment comes from experience;
[log in to unmask]       |  experience comes from bad judgment.
                             |        -- Mark Twain

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