Path: news.daimi.aau.dk!glad From: news@daimi.aau.dk Newsgroups: comp.lang.beta Subject: News from mail Date: 28 Dec 1995 15:38:05 GMT Organization: DAIMI, Computer Science Dept. at Aarhus University Lines: 32 Approved: mailtonews@daimi.aau.dk Distribution: world Message-ID: <4budkt$qqu@krone.daimi.aau.dk> NNTP-Posting-Host: daimi.daimi.aau.dk In article <4bkilb$g47@netnews.upenn.edu> Wolfgang Ziller writes: > olevi@daimi.aau.dk (Ole Villumsen) wrote: > >There's another possibility: using an attributes slot. > > > >myClass: (# <> > > > > 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 <> which > only allows *one* attribute to be added. > > Has this problem been fixed in the current implementation > or is the limitation still in place? F08 in the FAQ refers to the grammar, not the compiler. The fragment system is part of the implementation and has an alias between and , i.e. the above is possible. (On the other hand, I don't know why the grammar would be ambiguous if were allowed to generate itself.) Affi