Path: news.daimi.aau.dk!news.uni-c.dk!newsfeed.sunet.se!news00.sunet.se!sunic!news.sprintlink.net!newsfeed.internetmci.com!newsserver.jvnc.net!newsserver2.jvnc.net!netnews.upenn.edu!news
From: Wolfgang Ziller <wziller@math.upenn.edu>
Newsgroups: comp.lang.beta
Subject: Re: Adding methods without renaming the class (was Re: What's wrong with this picture?)
Date: 24 Dec 1995 21:59:17 GMT
Organization: University of Pennsylvania
Lines: 29
Message-ID: <4bkifl$g47@netnews.upenn.edu>
References: <4aodps$70h@netnews.upenn.edu> <4b6p2p$dua@fbi-news.Informatik.Uni-Dortmund.DE> <4b9apo$aop@krone.daimi.aau.dk>
NNTP-Posting-Host: ts11-20.upenn.edu
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Mailer: Mozilla 1.1N (Windows; I; 16bit)
To: olevi@daimi.aau.dk

[discussion on adding attributes to an existing class]

olevi@daimi.aau.dk (Ole Villumsen) wrote:
>There's another possibility: using an attributes slot.
>
>myClass: (# <<slot myClassLib: attributes>>
>
>            methodA: (# ... #)
>            ...
>         #);
>
>Such a slot allows you to define in a different fragment, additional
>methods for myClass, even if myClass is written by someone else,
>frozen and delivered to you.

However, the FAQ (v. 1.7) says that this is not possible
with the current compiler since certain ambiguities come up
by doing that.  To (partially) solve the problem, one is
allowed to write <<slot myClassLib: attributesDecl>> which 
only allows *one* attribute to be added.

Has this problem been fixed in the current implementation 
or is the limitation still in place?

Thanks,
Wolfgang Ziller