Re: Trouble with renaming types

["Bob McChesney" <bob@teambob.freeserve.co.uk>]

Hmm, maybe I'm doing it wrong then...

When I use the 1st method (i.e. new type of WordSet.Set) what you said about
inherited procedures doesn't seem to hold for me.

eg, I've instantiated WordSet.

So ... in WordSet I have:
a type defined called Set
a procedure Add(Set, Word)

I've made type Dictionary a new WordSet.Set (which it allows no problem).

BUT when I try and do:

WordSet(Dictionary, Word) I get the compilation error:

Expected private type "Set" .... found private type "Dictionary".

Any ideas?

Thanks
Bob

"Mark" <up.yerz@nospam.com> wrote in message
news:%oVJ6.129347$xN4.8316100@news1.sttls1.wa.home.com...
>
> "Bob McChesney" <bob@teambob.freeserve.co.uk> wrote in message
> news:9d949f$kto$1@newsg1.svr.pol.co.uk...
> > Oh, forgot to mention, I'm not using:
> >
> > 'type Dictionary is new WordSet.Set'
> >
> > because when I do that all the functions of WordSet cannot operate on
type
> > Dictionary.
>
> Yes and no... subprograms defined immediately within Wordset, if they
> operate on type Set, are "primitive operations" of Set and will be
inherited
> (think of that as "duplicated") for type Dictionary.
>
> But subprograms defined elsewhere that operate operate on Set are not part
> of type Set, so they can't be inherited by Dictionary.
>
> >
> > What I need is to be able to give type WordSet.Set a new name, but still
> > allow all oof the WordSet functions/procedures to be able to work on it.
> >
>
> To "alias" a type with an interchangeable name, say this:
>
>     subtype Dictionary is Wordset.Set;
>
> (note, no "new" in there... :-)
>
> Have fun,
> -- mark
>
>
>