Working great for me - thanks Laurent!
On Monday, 20 October 2014 21:22:31 UTC+8, Laurent PETIT wrote:
>
> Counterclockwise, the Eclipse Clojure development tool.
>
> Counterclockwise 0.29.0 has been released.
>
> Improvement over 0.28.1 based on user feedback.
> Also, upgraded Leiningen version t
On 20 October 2014 17:08, Phillip Lord wrote:
> James Reeves writes:
>
> > Clojure prefers "simple" solutions over "easy" solutions.
>
> A nice aphorism sometimes, but content free in this case, I think.
Well, no... The whole point is that "simple" and "easy" in this context
have objective def
>
> Well, the question is, where does this additional complexity come from.
> In Java, it results in enormous quantities of boilerplate get/set
> methods. In Scala, these are autocoded away.
>
Boilerplate isn't complexity: It's inefficiency.
I'll grant that it creates complexity-potential-ene
James Reeves writes:
>> Yes, which is what I have done, of course. Now it won't work in any IDE
>> which looks for the docstring as :doc metadata. It is totally
>> unextensible. I do not think that this is good.
>>
>
> Clojure prefers "simple" solutions over "easy" solutions.
A nice aphorism some
On 20 October 2014 14:02, Phillip Lord wrote:
>
> The uniform access principle is about having uniform access to data and
> APIs. It's not about prefering one or the other.
>
Right, but Clojure *does* heavily prefer data over APIs, and therein lies
the conflict.
> Yes, which is what I have don
Counterclockwise, the Eclipse Clojure development tool.
Counterclockwise 0.29.0 has been released.
Improvement over 0.28.1 based on user feedback.
Also, upgraded Leiningen version to 2.5.0.
ChangeLog
=
http://doc.ccw-ide.org/ChangeLog.html#_changes_between_counterclockwise_0_28_1_and_0
James Reeves writes:
>> > Yes, Clojure pretty much rejects the idea of uniform access.
>
>
>> I don't think it does. I think it just does not support it which is a
>> somewhat different thing.
>>
>
> I thought it was pretty clear that Clojure prefers data over APIs. The
> uniform access principle
On 20 October 2014 12:23, Phillip Lord wrote:
> James Reeves writes:
>
> > Yes, Clojure pretty much rejects the idea of uniform access.
> I don't think it does. I think it just does not support it which is a
> somewhat different thing.
>
I thought it was pretty clear that Clojure prefers data
On Monday, 20 October 2014, Phillip Lord
wrote:
>
> Interesting. So, if you resolve http://www.clojure.org, is this data or
> is it computed?
>
You're dereferencing a ref (url) to get an immutable value (string).
Maybe it would be worth exploring ways to implement IDeref with custom data
types?
James Reeves writes:
> On 18 October 2014 08:28, Mark Engelberg wrote:
>
>> Yeah, it's hard to deny the convenience of Clojure's keyword lookups and
>> standard assoc mechanism for getting and setting stored values, but I think
>> Bertrand Meyer's Uniform Access Principle reflects some pretty de
Fluid Dynamics writes:
>> I don't know who is the outlier. The point is that Scala, for instance,
>> has explicit support to hide the distinction between accessing a value
>> and computing a value. The point is to support the uniform access
>> principle.
>>
>> http://en.wikipedia.org/wiki/Unif
James Reeves writes:
> On 17 October 2014 16:21, Phillip Lord wrote:
>> http://en.wikipedia.org/wiki/Uniform_access_principle
>>
>> To my knowledge, Clojure cannot do this.
>>
>
> Yes, Clojure pretty much rejects the idea of uniform access.
I don't think it does. I think it just does not suppo
12 matches
Mail list logo
