detail.ftl?job=160789
For people unfamiliar with Teradata Loom, our team used to be with
Revelytix until the company was acquired by Teradata last year.
Regards,
Paul Gearon
--
You received this message because you are subscribed to the Google
Groups "Clojure" group.
To post to this
Hi Francesco,
I apologize for using "for" earlier, as I did not explain how you should be
using it. The comment of "do something with rel" should have indicated that
it resolved to an expression, and those expressions would be returned in a
seq (the "for" expression resolves to have a value of a s
Hi Francesco,
You want to decouple your code from the data that it is operating on, so
your code can operate regardless of the contents of the list. Otherwise,
you'll need code that matches the list, in which case it could all be code
anyway. Operating on arbitrary lists makes it easy to test simp
5, 2014 at 8:19 AM, Herwig Hochleitner
wrote:
> 2014-05-23 19:01 GMT+02:00 Paul Gearon :
>
>
>> I still argue for using keywords here. The existing API uses them, and
>> they're a natural fit.
>>
>
> The fact that they have established meaning (for denoting lit
I'll still have some
gaps in my knowledge.
On Thu, May 22, 2014 at 2:44 PM, Herwig Hochleitner
wrote:
> 2014-05-21 21:06 GMT+02:00 Paul Gearon :
>
>
>> Are QNames strictly necessary? Keywords seem to do the trick, and they
>> work in nicely with what already exists.
>
My understanding is that this is the central library for XML, so
theoretically it's preferred. This is why I'm trying to use it. Also, it's
one of the few implementations using StAX, which is the best way to do lazy
streaming (though core.async makes SAX a viable option again).
However, without na
Hi Herwig,
Thanks for the response.
I'll remove some of the less relevant bits as I reply inline...
On Wed, May 21, 2014 at 2:26 PM, Herwig Hochleitner
wrote:
> 2014-05-21 19:31 GMT+02:00 Paul Gearon :
>
>> I like the way that you have split the implementation of func
Hi Herwig,
I needed this myself and took a stab at it before it occurred to me to look
for other implementations and found yours.
I like the way that you have split the implementation of functionality into
different namespaces. The current release is a little monolithic.
One thing that bothers m
pported, as well as OWL/XML (:owl - which I don't
really know). I don't see Turtle though, which is the main interchange
format I try to use. Am I missing it?
Thanks!
Regards,
Paul Gearon
--
--
You received this message because you are subscribed to the Google
Groups "Clojure"
On Monday, 4 March 2013 01:50:56 UTC-5, edw...@kenworthy.info wrote:
> Okay, I think I understand that.
>
> Does that mean this code could never work as intended in a Clojure
> program, only at the repl (which seems a bit of a limitation) or is there a
> way to make it work as intended, generati
Since HelloWorld worked for me, I tried to output the command line
arguments as a string. Consequently, the program now looks like:
(ns cljshello.core
(:require [cljs.nodejs :as nj]))
(defn -main [& argv]
(println (str "Hello, World!" (.-argv nj/process) "\n")))
(set! *main-cli-fn* -main)
On Saturday, 17 November 2012 19:52:39 UTC-5, David Nolen wrote:
>
> What is the error under simple optimizations? Errors under advanced
> optimizations are not particularly informative :)
Good point, sorry.
Every minor change, is leading to significant differences, so I'm trying to
strip it
ction.Module._load (module.js:312:12)
at Module.runMain (module.js:492:10)
at process.startup.processNextTick.process._tickCallback (node.js:244:9)
Interestingly, it's printed the correct output, but fails after. Also, do I
mention in the same place that I get a different set of err
On Sat, Oct 23, 2010 at 5:16 PM, Paul Richards wrote:
> Hi,
> I have a multimethod which is dispatched on two arguments:
>
> (defmulti bar (fn [x y] [x y]))
> (defmethod bar [1 2] ..)
> (defmethod bar [3 4] ..)
>
> Is there a way I can define methods on this which use "wildcards"?
What about som
14 matches
Mail list logo
