Re: Visibility of Indexing aspects

["Randy Brukardt" <randy@rrsoftware.com>]

"Dan'l Miller" <optikos@verizon.net> wrote in message 
news:3eebe2fb-f066-4248-9b2f-1db32497fd82@googlegroups.com...
On Wednesday, July 25, 2018 at 2:58:44 PM UTC-5, AdaMagica wrote:
>> Much ado about nothing.
>>
>> The writer of this code erroneously put things in the private part which
>> should have been public. There is a compiler bug leaking from privacy
>>which seduced the writer into thinking that his wrong code is correct.
>>
>> The RM is very precise about this, see the references in this thread.
>>
>> Love's Labours Lost with any further discussion.
>
>In other words, I made an insightful good point ...

Sounds like babble to me. What's used by the client has to be public, 
period.

...
>The _LRM_'s forcing of {Reference, Reference_Holder, Container_Array, ...} 
>to be public declarations ...

...is perfectly fine -- there's nothing wrong or dangerous with using them 
directly. Indeed, "indexing" is just a shorthand for a longer call involving 
Reference -- you're always allowed to make the longer call, just like you 
are allowed to put in .all even if you could have omitted it. We went to 
substantial lengths to ensure that you can't keep a reference value longer 
than the existence of the return object from Reference -- regardless of how 
you use the package. (Telling people not to do something is never an 
effective technique for safety!)

If you have declarations that *can't* be used directly, then put them into 
the private part. But you're never supposed to be getting a half-and-half 
situation.

                                           Randy.