Re: (= function) evaluation steps

2016-12-17 Thread Rafo Ufoun
lementation). Thank you again, you helped me a lot ! Le samedi 17 décembre 2016 18:24:26 UTC-5, Alex Miller a écrit : > > > > On Saturday, December 17, 2016 at 3:54:07 PM UTC-6, Rafo Ufoun wrote: >> >> Is there a special check when the equality is asked on map ? >> >

Re: Closure for object pattern? A good idea?

2016-12-17 Thread Rafo Ufoun
Very clear thank you ! I can't wait to know these concept as I am discovering clojure with the 'Functionnal programming for OO programmer' book. Thank you again Le samedi 17 décembre 2016 18:53:31 UTC-5, James Reeves a écrit : > > On 17 December 2016 at 22:13, Rafo Ufoun

Re: Closure for object pattern? A good idea?

2016-12-17 Thread Rafo Ufoun
I'm a real newbe to clojure and functionnal programming but reading your answer raised a question : Where do you "store" the stopwatch object which you are passing to all your functions ? I understand that mutability is not needed to develop the functions you described but all of them take a

Re: (= function) evaluation steps

2016-12-17 Thread Rafo Ufoun
Is there a special check when the equality is asked on map ? I thought the evaluator evaluate all the expression the same way , by substituting each expression contained in the list to other evaluators. In the book, the author tells the substitution rule for function evaluation is responsible f

(= function) evaluation steps

2016-12-17 Thread Rafo Ufoun
Hi everyone, I'm reading the excellent 'Functionnal programming for OO programmer' and I encounter an issue understanding how the '=' function works. We have a 'Triangle' structure defined by a map of 'Point's so a Triangle is like {:point1 {:x 1 :y 1} :point2 {:x 1 :y 1} :point3 {:x 4 :y 2}}

Re: apply arguments

2016-12-14 Thread Rafo Ufoun
Ok now I understand ! So this implementation of apply act like this, and all implementations need, as the last arg of all the list, a sequence. Thank you Le mercredi 14 décembre 2016 13:59:40 UTC-5, James Reeves a écrit : > > On 14 December 2016 at 17:38, Rafo Ufoun > wrote: >

Re: apply arguments

2016-12-14 Thread Rafo Ufoun
ts. > > In most cases you don't need to use this technique because the performance > gain will be minimal. My print-all function above is probably going to > spend most of its time on I/O, making the optimisation all but useless in > my example. But clojure.core is used everywhere, so

apply arguments

2016-12-14 Thread Rafo Ufoun
Hi everyone, I'm new to clojure and I try to understand the apply function. >From the clojure sources, I can see that there are several signatures for this method: with or without additional arguments before the sequence. According to these signatures, we can have 4 arguments MAX before gettin