Integration of srfi-35 condition hierarchy and CLOS-style object system
If the implementation supports CLOS-style object system, it may be natural to map each condition type to each class. Then (condition-has-type? cond type) is just a (is-a? cond type). However, this might cause a problem with compound conditions.
If we want to keep condition-has-type? vs is-a? equivalence, (make-compound-condition cond0 cond1 ...) has to create a subclass that inherits all of (class-of condN). This means:
Different implementations seem to approach this differently.
About This Site
Concept:CaseSensitivity Concept:DocumentationFormat Concept:ExtendedLambdaList Concept:FileSystem Concept:FindAndAnyInCollection Concept:ForeignInterface Concept:HashTable Concept:Module Concept:Networking Concept:ObjectSystem Concept:Process Concept:RegularExpression Concept:UserGroup