Re: A non-primitive operation

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

A nested package is the usual way to do this, for the reasons that you 
stated.

Usually, the only routines that make sense to be treated that way are 
constructor functions (and even those may be better off being primitive, so 
that the generic dispatching constructor [or "factory"] can be used).

                            Randy.

"Victor Porton" <porton@narod.ru> wrote in message 
news:oufm3f$1s0q$1@gioia.aioe.org...
>I want a function F which returns a tagged type NOT to be considered as a
> primitive operation of T.
>
> Is there any other way for this, except to declare F in a separate 
> package?
>
> What about creating F in a subpackage? This way it could have access to 
> full
> view of T if T is private (an awful hack?):
>
> package X is
>
>  type T is tagged private;
>
>  package Sub is
>    function F return T;
>  end Sub;
>
> end X;
>
> Are there other ways?
>
> -- 
> Victor Porton - http://portonvictor.org