[J3] Question about C760

[Malcolm Cohen]

If unallocated or unassociated, there’s no object.  Just an empty descriptor.  You can’t pass something that’s not there.

 

Methods work on objects, not on arbitrary entities (functions, descriptors, meta-functions, conglomerations, whatever).  The idea just doesn’t make sense.

 

Cheers,

-- 

..............Malcolm Cohen, NAG Oxford/Tokyo.

 

From: J3 <j3-bounces at mailman.j3-fortran.org> On Behalf Of Van Snyder via J3
Sent: Thursday, November 8, 2018 6:16 AM
To: j3 <j3 at j3-fortran.org>
Cc: Van Snyder <Van.Snyder at jpl.nasa.gov>
Subject: [J3] Question about C760

 

I'm curious why C760 prohibits the allocatable attribute for the
passed-object dummy argument. This makes it impossible to have a
type-bound procedure whose job is to allocate the object, check status,
etc.

I can see the possibility that if a procedure that has an allocatable
passed-object dummy argument were inherited into an extension type, and
the declared type of the actual argument associated to the passed-object
dummy argument were an extension of the dummy argument type, allocating
it with the correct type would not be possible (or at least not easy).

A constraint that requires a procedure with an allocatable passed-object
dummy argument to be overridden in extensions would be more useful.

I think the same argument applies to pointer.



Disclaimer

The Numerical Algorithms Group Ltd is a company registered in England and Wales with company number 1249803. The registered office is: Wilkinson House, Jordan Hill Road, Oxford OX2 8DR, United Kingdom. Please see our Privacy Notice <https://www.nag.co.uk/content/privacy-notice>  for information on how we process personal data and for details of how to stop or limit communications from us.

This e-mail has been scanned for all viruses and malware, and may have been automatically archived by Mimecast Ltd, an innovator in Software as a Service (SaaS) for business.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mailman.j3-fortran.org/pipermail/j3/attachments/20181108/8ae5060d/attachment.html>