John Gabriele jmg3...@gmail.com writes:
Hi John,
That's how docs generated with the plugin look like:
http://userpages.uni-koblenz.de/~horn/funnyqt-docs/
Nice, Tassilo!
Thanks. :-)
Incidentally, it looks like most of the doc strings there are
pretty-much markdown-formatted.
Well,
How does that work: you appear to be iterating over two, unconnected,
vectors.
And yes that's an example of the second option but doesn't explain if or
why that's the best approach- which was the question ;)
On Thursday, 18 April 2013 19:48:40 UTC+1, Alan Malloy wrote:
(for [[y cols]
Hi,
How about this?
(map-indexed (fn [i x] (vector x)) (for [x (range 10)] HELLO WORLD))
([HELLO WORLD] [HELLO WORLD] [HELLO WORLD] [HELLO WORLD] [HELLO
WORLD] [HELLO WORLD] [HELLO WORLD] [HELLO WORLD] [HELLO WORLD]
[HELLO WORLD])
Quinta-feira, 18 de Abril de 2013 11:14:19 UTC+1,
I also like the new api design. You can just jdbc/execute! and jdbc/query
everything. Or almost. I was trying:
(jdbc/execute!
[INSERT INTO fruits (name, color, flavor) VALUES (?, ?, ?) [apple
red sweet] [pear yellow sweet]])
But that doesn't work. Should it? I know that jdbc/insert! works
Both `for` and `doseq` support the same vector form preceding a body. `for`
returns a lazy sequence and is often appropriate for a purely functional
body. `doseq` is not lazy and returns nil, so it is only appropriate when
you want to run the body for side effects.
Take a look at
As a relatively new Clojure user, I have a relatively simple app which
parses a complex JSON structure into a database.
I have test code which verifies all the basic database functions, but I'm
not sure how best to exercise all the parsing code. The JSON parser is
built-in, and most of my
On Friday, April 19, 2013 3:16:58 AM UTC-4, Tassilo Horn wrote:
I think the final output would look better if you assumed the
docstrings themselves were markdown-formatted and rendered them as
html. (That is, only have the items under Arglists in a preformatted
block --- everything
I use
(defn get-conn []
(let [conn (make-connection (:database db-config)
:host (:host db-config)
:port (:port db-config)
(mongo-options :auto-connect-retry true))]
(auth conn)
conn))
try to
I am new to the Clojure world. After years of developing finance
applications in R, I am trying to convert a relatively big R/Finance
project into Clojure/Incanter. Some things are going very smoothly. I can
see how the number of LOC is drastically reduced and the code is clean and
concise.
I'm a little unclear as to what your specific challenge is. I understand
you're trying to test fns that take a map produced by the JSON parser, and
extract specific fields.
Would it be sufficient to just create literal maps to fake the output of
the JSON parser, use those as inputs to your
Hi all,
I wrote a bubble-sort program in clojure:
(defn bubble-sort
[col]
(letfn [(outter-loop
[cc i]
(if ( i 1)
cc
(letfn [(inner-loop
[c j]
(if ( j (- i 2))
c
I don't know about the speed, but I suspect the stack overflow results from
many nested calls to concat, which will by itself result in stack overflows.
On Fri, Apr 19, 2013 at 9:57 AM, Miles Wen miles.w...@gmail.com wrote:
Hi all,
I wrote a bubble-sort program in clojure:
(defn bubble-sort
Hi David ;
Thanks for your attempt to answer my question despite lack of information.
I was accessing my clojure application via apache virtual host. Any html
file served as a resource ends up with content type being text/plain .
Without apache everything works fine. I ended up doing something
The problem is that the current behavior is not consistent with what
you describe. Sometimes it fails, but sometimes it works when it
should fail.
And there's no documentation or guidelines about the current behavior
at all, so it's all very confusing.
My opinion is that interop is essentially
Does the exact same code work connecting directly to a single instance
or a to a replica set (instead of mongos shard server)?
On Fri, Apr 19, 2013 at 7:17 AM, Zhi Yang zhi.y...@yottaa.com wrote:
I use
(defn get-conn []
(let [conn (make-connection (:database db-config)
I agree with you that matching exactly the java method signatures
would be less confusing. I was advocating this to be as transparent
as possible with interop. I was in minority :)
Reviewing what I said, case 1b is a bit more complex, the compiler cannot
decide between the two methods case (byte
Welle [1] is an expressive Clojure client for Riak with batteries included.
1.5 is a 100% backwards compatible release that includes support for
retriers, conflict resolvers and a few minor improvements.
Release notes:
http://blog.clojurewerkz.org/blog/2013/04/19/welle-1-dot-5-0-is-released/
Month after month there are more and more people who announce their open
source
Clojure projects. This is great and we can't get enough of this.
What is not great is how easy it often is to get started with some of the
projects.
Some of the most basic maintainer best practices are completely
Old thread but what the heck... it doesn't work in my REPL
user= (defn key-pattern
#_= Create a regex Pattern of the form 'key1|key2', the key
names
#_= will be quoted in case they contain special regex characters
#_= [m]
#_= (- (keys m)
#_= (map
I just tried the code in a fresh REPL with Clojure 1.5.1 and it works,
so I tried it with Clojure 1.4.0 and it works. Well, assuming you do
this first: (require '[clojure.string :as s])
What version of Clojure are you using? Are you doing the require? Do
you have something else defined as `s`?
I fired up a Clojure 1.5.1 REPL, did (require '[clojure.string :as s])
first, then copied and pasted those two function definitions, and did not
get the errors you are seeing. I don't have a good guess why you are
getting those errors. Did you do the require first? What version of
Clojure are
Some background, I'd like to write a Clojure Jersey generator. Here's some
examples of Jersey:
http://jersey.java.net/nonav/documentation/latest/jax-rs.html#d4e188 To me
it seems like it's like compojure but more verbose. Since Jersey needs a
class and methods with specific annotations on
TL:DR
Write ideas for humans around your code or it will die.
Explain, don't document.
Excellent blog post. However, you write
Passing It Over
At some point you may become disinterested in maintaining your
project. Maybe you've moved on to a new job or no longer use
yes, it works for single instance, and for mongos, if I query use
fetch-one it works, just do not work for fetch
On Saturday, April 20, 2013 2:54:43 AM UTC+8, Sean Corfield wrote:
Does the exact same code work connecting directly to a single instance
or a to a replica set (instead of mongos
Hi Fernando,
Would just like to point out for those not yet aware that there is a group
of people interested in bringing proper multi-dimensional matrix
capabilities to Clojure in the core.mtarix project. Somewhat inspired by
NumPy, but with a distinctively Clojure flavour. See the discussion
Good points. I've tried to follow many of these with code I've written,
but there are still some things I could stand to do better.
Thanks for writing this, it can serve as a checklist for my own projects
from now on!
Cheers,
DD
(2013/04/20 7:09), Michael Klishin wrote:
Month after month
2013/4/20 u1204 d...@axiom-developer.org
There is a HUGE gulf between the user documentation and maintaining
the code. Just like there is a huge difference between using a car
and maintaining a car.
There are two things to consider:
* Your audience is other developers.
* Most projects are
2013/4/20 Ryan Neufeld r...@thinkrelevance.com
Find more details on making contributions in our contribution guidelines
here: https://github.com/pedestal/docs/blob/master/CONTRIBUTING.md
Happy Hacking,
Ryan @ Relevance
Ryan,
I'd like to thank everyone at Relevance for making this happen.
28 matches
Mail list logo
