Re: Proposed change to BC iterator parameters [limitedness]

[Georg Bauhaus <sb463ba@l1-hrz.uni-duisburg.de>]

amado.alves <amado.alves@netcabo.pt> wrote:
: 
:
: I do like indefinite formals, but I pass well
: without limited ones. Most limited formals I've seen in libraries
: are accompanied by a formal assignment operation or some such,
: which prety much defeats the purpose of their (formal) limitedness,
: i.e. their logic is in clash with their definition. 

Sometimes I dearly wanted limited records but was defeated
by the library that could not store them (storing them was the
intention):

  type T(x: access D) is tagged limited private;

I want x to be constant plus initialised once and for all,
so access discriminants are just fine, but T has to
be limited then. Which would have been o.K., but not every library
allows this.

What should I do? Use pointers to the records? Afaics, this leads to
allocators or library level declarations (not always possible when
an unkown number of objects' lives start during the program's run?)
or 'unchecked_access.

Or use record compontens of
  type D_Ptr is access constant D;
and get rid of the access discriminants, and have a definite type?
How do I prevent then that tagged records can be declared but not
initialised?

Any suggestion would be very welcome.


Thanks,
-- Georg