>
>
>
>
>> I’d really like a dependency system that makes each dep’s transitive
>> dependencies only visible to itself, so there would never be any reason to
>> resolve dependencies.
>>
>
> You need classloader support for this and indeed this is what OSGi and
> some early versions of the Jav
You might also have a look at a library called vinyasa
> https://github.com/ardumont/vinyasa
>
You can can add it to your lein profile to copy functions into clojure.core
and prefix them.
The prefix makes it very clear that these are not part of standard
clojure.core.
(inject 'clojure.cor
I am using a groovy library that returns a LinkedHashMap containing ArrayLists
and nested LinkedHashMaps. I did not expect any issues working with this in
clojure since this type implements java.util.Map I figured everything would
just work. However the first thing I tried to do was apply
cloj
5 16:19:40] (c) Copyright ZeroTurnaround OU, Estonia, Tartu.
[2012-05-05 16:19:40]
[2012-05-05 16:19:40] Over the last 1 days JRebel prevented
[2012-05-05 16:19:40] at least 1 redeploys/restarts saving you about 0
hours.
[2012-05-05 16:19:40]
[2012-05-05 16:19:40] This product is licensed t
When i first upgraded to clojure 1.4 i had a similar issue with lein not
downloading updated dependencies. It tirned out to be an invalid version range
dependency spec in midje that caused it to fail silently. Perhaps try removing
all other dependencies first and try again.
--
You received th
On Sunday, May 6, 2012 5:08:51 PM UTC-6, Anton Arhipov wrote:
>
> Tried both:
>
> "java -javaagent:... -jar clojure.jar" and "java -javaagent:... -
> cp ... clojure.main -r"
>
> Both seem to work fine. What does "java -version" print?
>
> java version "1.6.0_31"
>
> Java(TM) SE Runtime E
Done. Thanks.
--
You received this message because you are subscribed to the Google
Groups "Clojure" group.
To post to this group, send email to clojure@googlegroups.com
Note that posts from new members are moderated - please be patient with your
first post.
To unsubscribe from this group, send
When I first started my project I tried using defrecord and defprotocol for
various data structurs and when I wanted an easy serialization function I
used pr-str and read-string, this worked great!... until I wanted to do
some refactoring and move some types to another namespace. After changing
You could also (dorun (map f coll))
It is actually interesting you brought this up as I was recently
contrasting the OO principle "tell don't ask" with the functional way of
doing things. In OO a void method taking a visitor is preferred over
return values. One could perhaps say that (doru
On Tuesday, June 12, 2012 2:18:03 AM UTC-6, Christophe Grand wrote:
>
> Hi,
>
> To contrast our experiences of the language and the different approaches
> to deal with some problems:
>
> On Sun, Jun 10, 2012 at 4:47 AM, Kurt Harriger wrote:
>
>> Many will say tha
On Wednesday, June 13, 2012 2:52:15 AM UTC-6, Vinzent wrote:
>
> I do use pre-conditions where the test condition is simple, ie is this a
>> string? does the map have a :field-type? however I get a lot of my input
>> data from http requests as json which have similar structures but different
>
On Saturday, June 16, 2012 12:26:34 PM UTC-6, Sean Corfield wrote:
>
> On Sat, Jun 16, 2012 at 10:58 AM, Kurt Harriger
> wrote:
> > How does one turn off pre/post conditions in production?
>
> (binding [*assert* false] (call-my-code))
>
>
> I agree with S
On Saturday, June 16, 2012 1:28:21 PM UTC-6, Vinzent wrote:
>
> I agree, an explicit type field makes dispatching easy. However this data
>> structure returned by (http/get ... :as json) so if I want to add type
>> information I need to walk the tree and rewrite it. Not necessarily a bad
>>
--
Kurt Harriger
Sent with Sparrow (http://www.sparrowmailapp.com/?sig)
On Saturday, June 16, 2012 at 3:07 PM, Kurt Harriger wrote:
>
>
> On Saturday, June 16, 2012 1:28:21 PM UTC-6, Vinzent wrote:
> > > I agree, an explicit type field makes dispatching easy. Howeve
On Jun 16, 2012, at 6:27 PM, Softaddicts wrote:
> 50 years of solid programming principles, OO being the Holy Grail ? :)
>
> I assume then that you programmed a lot in Simula-66 ? I did...
>
> For over 50 years, we made the same mistakes that Clojure attempts to
> correct. Most of the time new la
On Sunday, June 17, 2012 8:48:58 AM UTC-6, Vinzent wrote:
>
> Well, if those assertions are violated, you can't do anything with it
> anyway - you program is written wrong and you have to release new version
> which'll fix it.
>
Yes, but if data in your database become corrupt then you may nee
On Sunday, June 17, 2012 9:09:23 AM UTC-6, Vinzent wrote:
>
> This still requires changing your code to @(:emails contact). If you use
(emails contact) you need change your code in only one place.
>>>
> The name "emails" implies that it's a sequence. Lazy sequence.
>
Yes it is... e
On Jun 17, 2012, at 10:45 AM, Vinzent wrote:
Yes it is... emails was not the best example in this case.. think the
> "area" example instead as this is single value rather than collection.
>
Well, I thought we've already came to the agreement that area is a
(polymorphic) function and it has nothi
Sent from my iPhone
On Jun 17, 2012, at 12:43 PM, Vinzent wrote:
Data structure is an implementation detail...
>
It's not. Not in clojure. It is in OO, but clojure is not an OO language,
so it's not an implementation detail in clojure.
That is my point, representations SHOULD be considered im
On Sunday, June 17, 2012 1:41:22 PM UTC-6, Vinzent wrote:
>
> That is my point, representations SHOULD be considered implementation
>> details, because representations change... if you treat them as contracts
>> your code will break everywhere, if you wrap them with abstractions your
>> code w
On Sunday, June 17, 2012 6:31:34 PM UTC-6, Sean Corfield wrote:
>
> On Sun, Jun 17, 2012 at 11:59 AM, Kurt Harriger
> wrote:
> > That is my point, representations SHOULD be considered implementation
> > details, because representations change... if you treat them as
On Jun 17, 2012, at 9:38 PM, Timothy Baldridge wrote:
>>> I have also found that clojure code lacks cohesion we hate objects so we
>>> are just going to throw everything into one large namespace and say we have
>>> none... In OO I might call this a god class? I don't know, I'm not sold
>>> ye
On Jun 17, 2012, at 9:46 PM, Sean Corfield wrote:
> On Sun, Jun 17, 2012 at 8:06 PM, Kurt Harriger wrote:
>> One of the sayings I hear reiterated is "it is better to have 100 methods
>> that operate on one data structure than 10 methods that operate on 10 data
>> str
On Jun 18, 2012, at 2:09 AM, Christophe Grand wrote:
On Sun, Jun 17, 2012 at 8:59 PM, Kurt Harriger wrote:
>
> Data structure is an implementation detail...
>>
>
> It's not. Not in clojure. It is in OO, but clojure is not an OO language,
> so it's not an i
I did not know about lazy map either… This might be exactly what I was
needed. Maps with referentially transparent properties rather than fields.
A way to make minor changes to map representation without adding an api in
advance, introducing breaking changes, redundant properties, or conver
On Monday, June 18, 2012 8:01:47 AM UTC-6, tbc++ wrote:
>
> > Isnt that just creating an api? Everywhere the old model exists you need
> to
> > call a function to create the desired data structure and this adds
> another
> > layer of complexity that needs maintained. Not all conversions are
On Jun 18, 2012, at 5:35 PM, Softaddicts wrote:
> Lets talk a bit about my world here.
>
> We created a product to link medical equipments
> using a variety of protocols, some talk HL7, DICOM, others have proprietary
> means to
> access data from various places.
>
> From the start we chose the r
27 matches
Mail list logo
