Somehow, I just knew someone was going ask "why...?" :-) A while back, I constructed a little mechanism for defining data types, built on top of the protocol/record/type mechanism. Under certain circumstances, it generates protocols with no methods, basically in situations where it wants to identify a class of types as such, but those those types have no common methods that aren't already part of other protocols. Sounds strange, and probably is; but it's basically a manifestation of the fact that a protocol isn't just a collection of methods, but a property that can be tested, e.g., with satisfies?.
Heh... An explanation that's several orders of magnitude more pretentious than the rather humble reality. In the end, it's not a huge deal to work around (it's not that hard to generate a dummy method), but it's just another set of tedious special cases to deal with. Thanks for the response! -- Howard -- You received this message because you are subscribed to the Google Groups "Clojure" group. To post to this group, send email to [email protected] Note that posts from new members are moderated - please be patient with your first post. To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/clojure?hl=en
