On Fri, 2015-09-18 at 14:48 +0200, Marcus Denker wrote:
> > > >
> > >
> > > What I did is to implement #isUsed like this in e.g the hierarchy
> > > of RBLintRule:
> > >
> > > isUsed
> > > "all my sublasses are used"
> > > ^self name ~= ‘RBLintRule'
> > >
> > > this way if RBLintRule is not used, it is seen by the Critique,
> > > but all subclasses
> > > are used by default.
> > >
> > > I implemented that in TestCase, too, and removed the explicit
> > > check for TestCase
> > > subclasses from the rule.
> >
> > This is a nice thing. In the same way we can deal with abstract
> > classes. So if someone develops an abstract class with an intent to
> > use it, he can specify that it’s ok to use the class.
> >
>
> True.
> > Also is there any work on pragmas for classes, at some point I’ve
> > heard something about it but can’t recall.
> >
> Yes, the question is where to put it syntactically
After a class declaration like this:
LLVMDisposableObject subclass:#LLVMDIBuilder
instanceVariableNames:''
classVariableNames:''
poolDictionaries:'LLVMModuleFlagBehavior'
category:'LLVM-S-Core'
Annotation key: 'disposable:' value: 'true'
This ANSI-compatible way (see page 39 of NCITS J20 DRAFT
of ANSI Smalltalk Standard, rev 1.9).
Perhaps nice way is
Annotation disposable: true
> and how to save it in monticello…
In the source as above. In the binary, in a separate
entry in the .zip so the other MC implementation won't
crash but silently ignore them.
