Greg Williams wrote: > easy to see which one will be used. By providing a single location where > /ALL/ overloaded packages would go (VIRTUALZONE::${PACKAGE}), you limit > yourself in the amount a class (or class collection) may be extended. VIRTUALZONE:: was an example; the virtual root could have any name, meaning that any number of ISA hops could be required before resolution. -- David Nicol 816.235.1187 [EMAIL PROTECTED] "A taste so good that we stand behind every bottle and can."
- Re: RFC 254 (v1) Class Collections: Provide the ability ... Michael G Schwern
- Re: RFC 254 (v1) Class Collections: Provide the abi... Nathan Wiger
- Re: RFC 254 (v1) Class Collections: Provide the... Greg Williams
- Re: RFC 254 (v1) Class Collections: Provide the... Damian Conway
- Re: RFC 254 (v1) Class Collections: Provide... Greg Williams
- Re: RFC 254 (v1) Class Collections: Provide... Damian Conway
- Re: RFC 254 (v1) Class Collections: Provide the abi... Greg Williams
- Re: RFC 254 (v1) Class Collections: Provide the... David L. Nicol
- Re: RFC 254 (v1) Class Collections: Provide... Mark Summerfield
- Re: RFC 254 (v1) Class Collections: Provide... Greg Williams
- David L. Nicol