On Feb 28, 7:36 pm, reynard wrote:
> Perhaps my choice of function names (abstract and concrete) for my
> original post is not very appropriate. I did not mean to apply the OO
> concept of abstract class, abstract methods, etc. Since it seems that
> my original post did not convey my query cle
Perhaps my choice of function names (abstract and concrete) for my
original post is not very appropriate. I did not mean to apply the OO
concept of abstract class, abstract methods, etc. Since it seems that
my original post did not convey my query clearly, I would try to
depict it with some "conc
Perhaps my choice of function names (abstract and concrete) for my
original post is not very appropriate. I did not mean to apply the OO
concept of abstract class, abstract methods, etc. Since it seemed
that my original post did not convey my query clearly, I would try to
depict it with some "co
If anything, the defprotocol and deftype stuff that's on the way is
more along the lines of an abstract class because you can define a
protocol, acting a sort of modularized interface, and then you can
compose types by grouping together functions that implement one ore
more protocols. Anyway, I do
On Feb 27, 9:10 pm, reynard wrote:
> This may be more about functional programming in general, rather than
> clojure specific. However, since I mainly use clojure for learning
> functional programming, I would like to discuss it here.
>
> Basically, I can think of the following 2 ways of doing ab
This may be more about functional programming in general, rather than
clojure specific. However, since I mainly use clojure for learning
functional programming, I would like to discuss it here.
Basically, I can think of the following 2 ways of doing abstraction.
I would like to hear some comments
