I was looking at the pragma processor in SqMoose and noticed that there is a subclass of FMPragmaProcessor called MSEPragmaProcessor. Now this class does nothing except override one method from FMPragmaProcessor, which is almost a copy-paste of its overridden method. The only difference between the two methods is that one have an early abort condition while the other continues even if the condition is met.
Now MSEPragmaProcessor is packaged in Moose-Finder (and is used by mooseDescription). I wonder what is the intent behind this class?
-- Simon
Hi Simon,
The Fame Pragma Processor will crash if there is no method to describe the class. This might make some sense when you talk about well describe classes, but in the general context of adding meta- descriptions to Smalltalk it does not make sense.
In particular, in the MooseFinder you do not want to crash if you stumble across a non-described object, but rather you want to just display nothing or maybe even ask for what to show.
I created MSEPrgamaProcessor to not interfere with the default behavior of Fame, but to also not affect the wanted behavior of Moose. However, I do agree that it should not be in Moose-Finder, but in Moose-Core :)
Cheers, Doru
On Feb 13, 2009, at 6:35 PM, Simon Denier wrote:
I was looking at the pragma processor in SqMoose and noticed that there is a subclass of FMPragmaProcessor called MSEPragmaProcessor. Now this class does nothing except override one method from FMPragmaProcessor, which is almost a copy-paste of its overridden method. The only difference between the two methods is that one have an early abort condition while the other continues even if the condition is met.
Now MSEPragmaProcessor is packaged in Moose-Finder (and is used by mooseDescription). I wonder what is the intent behind this class?
-- Simon
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
-- www.tudorgirba.com
"It's not how it is, it is how we see it."
-
Simon Denier -
Tudor Girba