Hi Luca and Phil,
Thanks for your insights.
Especially your example, Phil, is very revealing.
I think I now have a direction for further thought. And of course I did not
expect there to be a 'magic silver bullet' answer to the question.
Cheers,
Christian
--
You received this message because
Christian Eitner <7enderh...@gmail.com> writes:
>>
>> Hi Christian,
>> I think you are looking for this.
>>
>> http://en.wikipedia.org/wiki/Facade_pattern
>>
>> In clojure you can use a def for each private member of the facade.
>> Alternatively you can write a function to instantiate and return
Hi Christian,
I've been a bit too technical. What I mean is give your OO system a new
interface made of functions. Choose functions according to your needs and
develop a layer of functions that can create and access your objects
instances. It's my opinion this is the stateful bridge in your firs
Hi Luca,
On Thursday, April 3, 2014 11:57:27 AM UTC+2, icamts wrote:
>
> Hi Christian,
> I think you are looking for this.
>
> http://en.wikipedia.org/wiki/Facade_pattern
>
> In clojure you can use a def for each private member of the facade.
> Alternatively you can write a function to instantiat
Hi Christian,
I think you are looking for this.
http://en.wikipedia.org/wiki/Facade_pattern
In clojure you can use a def for each private member of the facade.
Alternatively you can write a function to instantiate and return private
members. Use a defn for each facade's methods.
Luca
Il giorn
Hello everybody,
Given an enormous network of inter-referenced, mutable objects which have
to change in-place driven by events (= the OO system).
Which strategy would you recommend to plug into such a system with Clojure,
building an island of immutable functional programming saneness? How to
