On Wed, 3 Mar 2010 09:47:09 -0800 (PST)
cageface <[email protected]> wrote:
> I've been reading through the examples of "OO" in clojure using multi-
> methods and they certainly seem very flexible and powerful. I'm
> wondering, however, how people handle interface & library design. If
> people can implement "objects" as maps, structs, or just about
> anything else you can discriminate on via a dispatch function, how do
> you handle code reuse and sharing of libraries. If we're all using our
> own home-grown OO systems how do we communicate?
I hope that most people aren't using home-grown OO systems for most of
their problems - especially given that maps are almost enough for a
prototype-based system to start with. That would be working "against
the grain", as it were. While it would be nice to have a standard OO
system for the cases where that's appropriate, those should be
relatively rare.
<mike
--
Mike Meyer <[email protected]> http://www.mired.org/consulting.html
Independent Network/Unix/Perforce consultant, email for more information.
O< ascii ribbon campaign - stop html mail - www.asciiribbon.org
--
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
