On Mon, Mar 5, 2012 at 12:50 PM, Phil Hagelberg p...@hagelb.org wrote:
Sorry, that wasn't too clear. Using :plugins is the correct approach here.
Awesome, that works with the new buildpack. Thanks!
I also had to set up AOT compilation to avoid the boot timeout
mentioned in my original post.
Awesome - I wonder if Frinj was what Rich had in mind when he was giving
that talk?
On Sunday, 4 March 2012 19:08:36 UTC+11, martintrojer wrote:
And now there is Frinj! :)
https://github.com/martintrojer/frinj
On Monday, 21 June 2010 12:46:55 UTC+1, Julian wrote:
Rich Hickey made
On Tue, Mar 6, 2012 at 3:17 PM, Julian juliangam...@gmail.com wrote:
Awesome - I wonder if Frinj was what Rich had in mind when he was giving
that talk?
Rich was talking about Frink[1] which is an inspiration for Frinj.
Regards,
BG
[1] http://futureboy.us/frinkdocs/
--
Baishampayan Ghose
Awesome stuff! Great work...
Sam
---
http://sam.aaron.name
On 6 Mar 2012, at 03:05, Dave Ray wrote:
Hi,
Seesaw 1.4.0 is out now. The release notes [1] have highlights of all
the changes since 1.3.0. Note there are two breaking changes in the
API. I believe the impact of these changes
Recently I was studying Stuart Sierra's clojure-hadoop project¹, and
there saw a technique that I'd like to discuss. There's a Java class
generated whose method definitions get patched based on a provided
configuration, and I'd like to understand the scope of this patching and
why the technique's
Hi Steven
just fyi - more recent version of clojure-hadoop is available at
https://github.com/alexott/clojure-hadoop - it includes many
patches/improvements
On Tue, Mar 6, 2012 at 5:18 PM, Steven E. Harris s...@panix.com wrote:
Recently I was studying Stuart Sierra's clojure-hadoop project¹,
Marginalia v0.7.0 Release Notes
===
Marginalia is an ultra-lightweight literate programming tool for Clojure
inspired by [docco](http://jashkenas.github.com/docco/)*.
To get a quick look at what the output looks like, [visit the official
Marginalia
I kind of accidently discovered that you can create keywords with an embedded
space… not sure if that's a good idea, but you can:
user= (def k (keyword jaja nee))
#'user/k
user= (str k)
:jaja nee
user= (name k)
jaja nee
user= (keyword? k)
true
user= (keyword? :jaja nee)
CompilerException
CORRECTION: def form should be
(def a-var The docstring value)
--
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
I don't think you're supposed to use spaes in keywords.
On Tue, Mar 6, 2012 at 20:48, Frank Siebenlist
frank.siebenl...@gmail.com wrote:
One other option I should have tried before:
user= (pr-str k)
:jaja nee
user= (read-string (pr-str k))
:jaja
user=
but unfortunately that doesn't help
Fogus, congratulations on the release. My thanks to you and all the
contributors. Marginalia rules.
--
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
I don't think you're supposed to use spaces in keywords.
Using spaces in keywords is completely valid, as is using spaces in
symbols. You just have to be aware that there may be times when you
can't represent them in a literal form. pr-str could be extended to do
this though:
(pr-str :foo)
Those are convincing arguments/examples that spaces should be allowed in
keywords.
Your solution to enhance pr:
(pr-str k) ; as in your example
(keyword jaja nee)
should work.
Btw., symbols seem to have the exact same issue:
user= (def s (symbol with space))
#'user/s
user= s
with space
user=
I don't think you're supposed to use spaces in keywords.
Using spaces in keywords is completely valid, as is using spaces in
symbols.
Legal characters in keywords and symbols are documented at
http://clojure.org/reader :
Symbols begin with a non-numeric character and can contain
Symbols begin with a non-numeric character and can contain alphanumeric
characters and *, +, !, -, _, and ? ... Keywords are like symbols ...
But this is the documentation for the reader...not necessarily for
symbols/keywords.
My argument is that clojure in no way validates the input to
So… spaces are not allowed in symbol and keyword identifiers according to the
spec…
although Stu doesn't quote the phrase following the allowed chars, which reads:
(other characters will be allowed eventually…)
which seems to keep the door open for allowing spaces in the future (?).
If space
Timothy Baldridge tbaldri...@gmail.com writes:
I don't think you're supposed to use spaces in keywords.
Using spaces in keywords is completely valid, as is using spaces in
symbols. You just have to be aware that there may be times when you
can't represent them in a literal form. pr-str could
I am new to clojure. I am just trying to install and use feedparser-
clj. I ran lein install and it said it completed ok.
git clone git://github.com/scsibug/feedparser-clj.git
cd feedparser-clj/
lein install
...
Compiling feedparser-clj.core
Compilation succeeded.
Created
I was looking for something akin common lisps |weIrD SymBol!`| already,
too...
On 2012-03-06 15:28 , Frank Siebenlist frank.siebenl...@gmail.com
wrote:
SoŠ spaces are not allowed in symbol and keyword identifiers according to
the specŠ
although Stu doesn't quote the phrase following the allowed
While writing Clojure code, what Java classes, objects, and static
methods do you most often find yourself using?
--
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
Thank you for your help! :)
I managed to get repl/source-fn to read source from external namespace. But
print gives me
(defn buy? [today]\n (and\n(not (nil? today))\n
Everything on one line with \n instead of new lines. Shouldn't pretty
print handle this?
Best wishes
Nikem
On
On Tuesday, March 6, 2012 11:18:50 AM UTC-5, Steven E. Harris wrote:
If this impact is global, is it the case that this software never needs
to accommodate instances of these generated classes with different
configurations?
I haven't looked at that code in a long time, but the answer is
If you are just printing it to the screen, print or println will do
what you want. There shouldn't be a need for a pretty printer, the
source is already formatted exactly as it was written.
On Tue, Mar 6, 2012 at 1:02 AM, Nikem gni...@gmail.com wrote:
Thank you for your help! :)
I managed to
Stuart Sierra the.stuart.sie...@gmail.com writes:
I haven't looked at that code in a long time, but the answer is yes. Each
Hadoop Job runs in its own JVM process.
Thank you. That makes sense, then.
Just to nail it home, though, do you agree that this patching technique
is generally /not/
If you are going to play with feedparser-clj from repl, maybe the best way
would be to run 'lein repl' inside feedparser-clj folder you just
downloaded. In this case, lein would automatically setup classpath for you.
However, if you are planning to use it inside your project, create it with
Hi,
Am 06.03.2012 um 21:28 schrieb Frank Siebenlist:
So… spaces are not allowed in symbol and keyword identifiers according to the
spec…
although Stu doesn't quote the phrase following the allowed chars, which
reads:
(other characters will be allowed eventually…)
which seems to
I've been playing around with the jarjar tool (
http://code.google.com/p/jarjar/
) in order to package my jar to avoid dependency conflicts with other
libs. It doesn't seem to work though with Clojure-created classfiles,
even when using aot compilation. At runtime, when doing a require/use
it
On Tue, Mar 6, 2012 at 7:36 AM, Bob bstewart...@gmail.com wrote:
I am new to clojure. I am just trying to install and use feedparser-
clj. I ran lein install and it said it completed ok.
You generally use Clojure libraries by specifying the dependency in
your project.clj file for Leiningen to
Meikel Brandmeyer m...@kotka.de writes:
I think this has been discussed several times in the past.
This is *not* a bug in keyword or symbol.
Here's the relevant issue:
http://dev.clojure.org/jira/browse/CLJ-17
Closed as declined in October, so I think it's safe to say the
you're on your
Thanks for the explanation - I tried to search for previous discussions and bug
reports about this issue before I posted, but it's clear I didn't look hard
enough...
I could still argue that there is a bug in the documentation that should spell
this out - especially when it has been discussed
I'm returning to Clojure in earnest for the first time since 1.1 (and
very happy to be back!). Apologies if this question revisits old
issues.
I'm trying to understand why the semantics of protocols are such that
the third statement here returns true:
user= (defprotocol Bashable (bash [this])
Tassilo Horn tass...@member.fsf.org writes:
So basically, in java unicode escapes are replaced before parsing,
whereas in clojure any unicode escape evaluates to a character, e.g.,
(\u002b 1 2) is (\+ 1 2), not (+ 1 2).
Well, I think the clojure way is the saner one. And if you really
need
32 matches
Mail list logo
