Method Annotations

Michael Rueger michael at squeakland.org
Sat Aug 23 19:00:24 UTC 2003


Michael Rueger wrote:

> Avi Bryant wrote:
> 
>> On Wed, 20 Aug 2003, Michael Rueger wrote:
>>
>>
>>> It would be absolutely valuable to have additional information
>>> associated with a method, but nothing that is active in any sense of the
>>> word.
>>

I found an excellent example of how this can break your system:

Morph class>>
noteCompilationOf: aSelector meta: isMeta
	"Any change to an additionsToViewer... method can invalidate existing 
etoy vocabularies"

	(isMeta and: [aSelector beginsWith: 'additionsToViewer']) ifTrue:
		[Vocabulary changeMadeToViewerAdditions]


*While* it is fileing in code this "sort-of-annotation" mechanism does 
somthing that reinitializes another, totally unrelated part of the 
system. Which, not surprisingly, doesn't work unless you carefully 
hand-order the methods in your filein. Hoping of course, that there is a 
  filein order that will work.

Michael




More information about the Squeak-dev mailing list