Re: Clojure list syntax sugar: f(x) notation
Am 30.12.2011 um 00:19 schrieb Softaddicts: > I suggest the Klingon downward triangle Natural delimiter you said ? :) And the irony that it is only used in latin transliteration… Meikel -- 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 email to clojure+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/clojure?hl=en
Re: Clooj is great :)
Hi Timothy, Thank you! I really appreciate your comments. I must admit there is still much left to be done on clooj and I haven't had much time to work on it of late. I thank everyone for their patience. Cheers, Arthur -- 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 email to clojure+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/clojure?hl=en
Re: Want some books or issues about ClojureCLR
Why God like dmiller don't write such a book? It must be very interesting. On Tue, Nov 29, 2011 at 8:45 AM, dmiller wrote: > The wiki on the github repo has some information about getting started > and how to accomplish some interop that is special to CLR. > > https://github.com/richhickey/clojure-clr/wiki > > and make sure to look at > > https://github.com/richhickey/clojure-clr/wiki/_pages > > for the complete list. > > Rob Rowe (http://rob-rowe.blogspot.com/, @rippinrobr) has been > blogging recently on getting started with ClojureCLR. > > -David > > > On Nov 28, 4:03 pm, Stuart Sierra wrote: > > Hi Adam, > > > > Clojure CLR is a community effort without official support. I am not > > aware of any books specifically about ClojureCLR. > > > > However, Clojure the *language* should be nearly identical between the > > JVM and CLR versions. Only interop with the host platform will be > > different. So any Clojure language book will be helpful in learning > > the language. > > > > Regards, > > -Stuart Sierra > > clojure.com > > -- > 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 email to > clojure+unsubscr...@googlegroups.com > For more options, visit this group at > http://groups.google.com/group/clojure?hl=en > -- 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 email to clojure+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/clojure?hl=en
ANN: deep-freeze serialization library
A few months back I released 1.0 of deep-freeze, a binary serialization library for Clojure. Due to recent additions by Peter Taoussanis I thought it would be about time to let some more people know about this project, and bump the version number to 1.2 deep-freeze is a simple serialization library that aims to be fast, generate concise data, and support as many Clojure structures as possible. Currently it outperforms read-string/print-str by quite a margin, supports (optionally) the "Snappy" Google compression library, and supports atoms, refs, and the standard Clojure structures. Support for deftype and defrecord, is not in yet, but is on the list. The data structure should not be considered stable by any means, as we will continue to optimize it as needed. But the actual API calls have stayed the same since version 1.0, and to be honest, it's such a simple lib, it can probably be copy and pasted into any lib anyone chooses. At any rate I thought it might come in useful for those experimenting with 0MQ, distributed computing, etc. Timothy Baldridge -- “One of the main causes of the fall of the Roman Empire was that–lacking zero–they had no way to indicate successful termination of their C programs.” (Robert Firth) -- 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 email to clojure+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/clojure?hl=en
Re: Really loving Clooj but..
On Thu, Dec 29, 2011 at 10:50 PM, Erlis Vidal wrote: > Cedric, you have a really good point, I just realized it after reading your > email. After sending the original email I saw what the error was, but what I > still unable to know is how could I debug from Clooj, other than using > println, any built-in trace a la LISP? > > I'm liking Clooj a lot, but really don't know how to debug there. Anyone? I wouldn't know. I rarely need to do more than look over the code, think about it, call functions from the repl with various inputs, examine stack traces, macroexpand-1, and occasionally slip in a println or two to solve problems and find and fix bugs. Making as much stuff as possible pure functions helps a lot, because pure functions can be tested in isolation and if they work then, they work period. -- 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 email to clojure+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/clojure?hl=en
Re: Really loving Clooj but..
Guys, Thanks so much for all the answers, thanks for taking the time to give me so many hints even when my email shows my Clojure ignorance. Cedric, you have a really good point, I just realized it after reading your email. After sending the original email I saw what the error was, but what I still unable to know is how could I debug from Clooj, other than using println, any built-in trace a la LISP? I'm liking Clooj a lot, but really don't know how to debug there. Anyone? Thanks one more Erlis On Thu, Dec 29, 2011 at 9:57 PM, Cedric Greevey wrote: > On Thu, Dec 29, 2011 at 6:23 PM, Mark Engelberg > wrote: > > I'd also like to know whether Clooj has any debug or stacktracing > > capabilities. Also, can the Clooj repl control the print level of > > infinite lazy structures? > > (set! *print-length* 20) > > (set! *print-level* 20) > > (.printStackTrace *e) > > Having shortcut buttons or keys for the latter, at least, would be > useful though. > > As for the original code, there is actually a bug in the function -- > namely, if an argument is nil (or false) it stops there without an > error message and without considering later arguments. Usually for a > loop like that I'd use (if more (let [x (first more)] ...)) in lieu of > if-let. That distinguishes the case more is nil from (first more) is > nil. The correct termination condition is more is nil, in this case. > The < comparison will then naturally blow up with an NPE or type error > if a nil makes it. > > An unfortunate feature of the original code, but hard to classify as a > bug, is that the < test is never performed, and thus no type error can > be generated, if there's only one argument -- which fact made it > harder for the OP to identify the nature of their conundrum. Harder > enough to end up posting here rather than instantly realizing what had > gone wrong, in fact. An explicit additional test at the fn start, such > as (if-not (instance? Number x) (throw ...)) would ensure an exception > throw if the only argument was nonnumeric. Or you could use a > precondition, which is exactly the tool for the job here. > > -- > 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 email to > clojure+unsubscr...@googlegroups.com > For more options, visit this group at > http://groups.google.com/group/clojure?hl=en > -- 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 email to clojure+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/clojure?hl=en
Re: Really loving Clooj but..
On Thu, Dec 29, 2011 at 6:23 PM, Mark Engelberg wrote: > I'd also like to know whether Clooj has any debug or stacktracing > capabilities. Also, can the Clooj repl control the print level of > infinite lazy structures? (set! *print-length* 20) (set! *print-level* 20) (.printStackTrace *e) Having shortcut buttons or keys for the latter, at least, would be useful though. As for the original code, there is actually a bug in the function -- namely, if an argument is nil (or false) it stops there without an error message and without considering later arguments. Usually for a loop like that I'd use (if more (let [x (first more)] ...)) in lieu of if-let. That distinguishes the case more is nil from (first more) is nil. The correct termination condition is more is nil, in this case. The < comparison will then naturally blow up with an NPE or type error if a nil makes it. An unfortunate feature of the original code, but hard to classify as a bug, is that the < test is never performed, and thus no type error can be generated, if there's only one argument -- which fact made it harder for the OP to identify the nature of their conundrum. Harder enough to end up posting here rather than instantly realizing what had gone wrong, in fact. An explicit additional test at the fn start, such as (if-not (instance? Number x) (throw ...)) would ensure an exception throw if the only argument was nonnumeric. Or you could use a precondition, which is exactly the tool for the job here. -- 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 email to clojure+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/clojure?hl=en
Re: Really loving Clooj but..
I'd also like to know whether Clooj has any debug or stacktracing capabilities. Also, can the Clooj repl control the print level of infinite lazy structures? Thanks, Mark -- 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 email to clojure+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/clojure?hl=en
Re: Clojure list syntax sugar: f(x) notation
I suggest the Klingon downward triangle Natural delimiter you said ? :) http://www.evertype.com/standards/csur/klingon.html Luc > Better yet we can say that function calls and forms always start with a > symbol and end with punctuation or some natural delimiter. So we could > write things like: > > defn f [x] > println "hi"! > 42; > . > > doseq [e range 10 20] >f e; > . > > map fn [x] Math/pow x 2.0, range 10. > > if even 3? > :even > :odd. > > No need for parens at all! > > -- > 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 email to > clojure+unsubscr...@googlegroups.com > For more options, visit this group at > http://groups.google.com/group/clojure?hl=en -- Softaddicts sent by ibisMail! -- 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 email to clojure+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/clojure?hl=en
Re: How to start using clojureCLR?
For VS integration, there is the following plugin. I haven't used it myself, so can't offer much help beyond this. Good luck! http://visualstudiogallery.msdn.microsoft.com/fb895809-2ae0-48aa-8a96-3c0d5b8e1fdc/ On Thursday, December 29, 2011 11:17:28 AM UTC-8, Erlis Vidal wrote: > > Hi! > > Thanks for the link. I really appreciate it. > > It looks like the CLR project is really in it first stage. Is someone > working on the tools? Any plans to integrate it with VS? > > thanks! and thanks for the CLR version! > > On Thu, Dec 29, 2011 at 2:04 PM, Benny Tsai wrote: > >> Hi Erlis, >> >> This is the most recent blog entry I've found w.r.t. getting up and >> running with Clojure CLR: >> >> >> http://www.myclojureadventure.com/2011/10/getting-started-with-clojure-clr.html >> >> What I really like about this particular blog is that the author has also >> written follow-up articles (in Nov. and Dec. of 2011) on how to do things >> like talk to SQL Server from Clojure CLR and how to call into Clojure CLR >> from C#. Hope this helps! >> >> >> On Tuesday, December 27, 2011 9:59:09 AM UTC-8, Erlis Vidal wrote: >>> >>> Hi group, >>> >>> I just joined the group and I'm really hypnotized with the Clojure >>> language. Most of the time in my day job I do .Net development but outside >>> of the job I'm always trying to learn and apply other languages and >>> technologies. The curse of the mainstream. >>> >>> I've just finished Stuart's book "Programming Clojure" and I would like >>> to start introducing some fun in my day to day programming, and when I saw >>> ClojureCLR I was really happy. >>> >>> The point is that I don't know where to start, I haven't found anything >>> that explain how to start working with it. Any blog on how to prepare the >>> environment and start using introducing clojure on my .Net projects ? >>> >>> I'm also curious about ClojureScript, I've been looking CoffeeScript and >>> there are some tools that even integrate with Visual Studio allowing to >>> generate the JavaScript file associate with the CoffeeScript, is there >>> anything like that for ClojureScript? Is it recommended to use >>> ClojureScript in the same scenarios as CoffeeScript or they should serve >>> different purposes? >>> >>> I probably should have two questions, but I see so many opportunities to >>> use Clojure right now that I don't want to miss anything. >>> >>> Thanks in advance and let me know where can I find some information, >>> even if you feel is irrelevant maybe for me is a gold mine. >>> Erlis >>> >> -- >> You received this message because you are subscribed to the Google >> Groups "Clojure" group. >> To post to this group, send email to clo...@googlegroups.com >> Note that posts from new members are moderated - please be patient with >> your first post. >> To unsubscribe from this group, send email to >> clojure+u...@googlegroups.com >> For more options, visit this group at >> http://groups.google.com/group/clojure?hl=en > > > -- 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 email to clojure+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/clojure?hl=en
Re: Really loving Clooj but..
Just add (println min) before if-let and you will see what is happening. Hubert. On Thu, Dec 29, 2011 at 10:23 PM, Erlis Vidal wrote: > Hi guys, > > I've using Clooj and following the labrepl but I'm hitting a wall right now. > How can I debug here? > > This the code I want to debug > > (defn min-1 [x & more] > (loop [min x > more (seq more)] > (if-let [x (first more)] > (recur (if (< x min) x min) (next more)) > min))) > > This is suppose to return the min value but it's not, It's returning me the > same sequence I'm passing: > > student.dialect=> (min-1 [1 2 3]) > [1 2 3] > > Even if you find the problem, don't forget to let me know how can I debug > here, so I can do it the next time > > Thanks > Erlis > > -- > 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 email to > clojure+unsubscr...@googlegroups.com > For more options, visit this group at > http://groups.google.com/group/clojure?hl=en -- 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 email to clojure+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/clojure?hl=en
Re: Really loving Clooj but..
2011/12/29 Erlis Vidal > Hi guys, > > I've using Clooj and following the labrepl but I'm hitting a wall right > now. How can I debug here? > > This the code I want to debug > > (defn min-1 [x & more] > (loop [min x > more (seq more)] > (if-let [x (first more)] > (recur (if (< x min) x min) (next more)) > min))) > > This is suppose to return the min value but it's not, It's returning me > the same sequence I'm passing: > > student.dialect=> (min-1 [1 2 3]) > [1 2 3] > > Even if you find the problem, don't forget to let me know how can I debug > here, so I can do it the next time > > Hello, I don't know how to do that with Clooj. Just wanted to let you know that with Counterclockwise ( Eclipse plugin ), you place a breakpoint on the if-let line, start in debugging mode, and the thread stops at the breakpoint, the "debug" perspective shows up, and the "Variables" view reveals that the 'min' variables contains a PersistentVector, where you'd expect a number => You're calling min-1 in the wrong way, you should have called it like (min-1 1 2 3), or (apply min-1 [1 2 3]) Cheers, Laurent > Thanks > Erlis > > -- > 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 email to > clojure+unsubscr...@googlegroups.com > For more options, visit this group at > http://groups.google.com/group/clojure?hl=en -- 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 email to clojure+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/clojure?hl=en
Re: Really loving Clooj but..
you are invoking the function in the wrong way what you really want to do is this: user> (min-1 2 1 3) 1 2011/12/29 Erlis Vidal > Hi guys, > > I've using Clooj and following the labrepl but I'm hitting a wall right > now. How can I debug here? > > This the code I want to debug > > (defn min-1 [x & more] > (loop [min x > more (seq more)] > (if-let [x (first more)] > (recur (if (< x min) x min) (next more)) > min))) > > This is suppose to return the min value but it's not, It's returning me > the same sequence I'm passing: > > student.dialect=> (min-1 [1 2 3]) > [1 2 3] > > Even if you find the problem, don't forget to let me know how can I debug > here, so I can do it the next time > > Thanks > Erlis > > -- > 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 email to > clojure+unsubscr...@googlegroups.com > For more options, visit this group at > http://groups.google.com/group/clojure?hl=en -- 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 email to clojure+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/clojure?hl=en
Really loving Clooj but..
Hi guys, I've using Clooj and following the labrepl but I'm hitting a wall right now. How can I debug here? This the code I want to debug (defn min-1 [x & more] (loop [min x more (seq more)] (if-let [x (first more)] (recur (if (< x min) x min) (next more)) min))) This is suppose to return the min value but it's not, It's returning me the same sequence I'm passing: student.dialect=> (min-1 [1 2 3]) [1 2 3] Even if you find the problem, don't forget to let me know how can I debug here, so I can do it the next time Thanks Erlis -- 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 email to clojure+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/clojure?hl=en
Re: Clojure list syntax sugar: f(x) notation
Better yet we can say that function calls and forms always start with a symbol and end with punctuation or some natural delimiter. So we could write things like: defn f [x] println "hi"! 42; . doseq [e range 10 20] f e; . map fn [x] Math/pow x 2.0, range 10. if even 3? :even :odd. No need for parens at all! -- 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 email to clojure+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/clojure?hl=en
Re: :arglists question
On Thu, Dec 29, 2011 at 11:27 AM, vitalyper wrote:
> My question is why do we have BOTH :arglists metadata and usual fn
> args destructuring?
As Meikel surmised, it's to improve the docstring (shown by the doc
function). We (the CongoMongo team) have not been terribly consistent
about it tho' :(
In the command function you highlighted, we show defaults for keyword
arguments (and the implication is that it takes two arguments: cmd and
a map - which is not the case). In the mongo! function, we show
keyword argument defaults more in line with usage:
{:arglists '([:db ? :host "localhost" :port 27017])}
[& {:keys [db host port]
:or {db nil host "localhost" port 27017}}]
In other functions, we just show the possible keyword arguments
without defaults:
;; create-collection!
{:arglists
'([collection :capped :size :max])}
([collection & {:keys [capped size max] :as options}]
;; fetch
{:arglists
'([collection :where :only :limit :skip :as :from :one? :count?
:sort :options])}
[coll & {:keys [where only as from one? count? limit skip sort options]
:or {where {} only [] as :clojure from :clojure
one? false count? false limit 0 skip 0 sort nil options []}}]
Hopefully you can see the intent...
--
Sean A Corfield -- (904) 302-SEAN
An Architect's View -- http://corfield.org/
World Singles, LLC. -- http://worldsingles.com/
"Perfection is the enemy of the good."
-- Gustave Flaubert, French realist novelist (1821-1880)
--
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 email to
clojure+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/clojure?hl=en
Re: :arglists question
Hi, Am 29.12.2011 um 20:27 schrieb vitalyper: > My question is why do we have BOTH :arglists metadata and usual fn > args destructuring? Probably to make things a bit clearer in the docstring. The usual destructuring is powerful but rather unreadable for a quick glance at the reference. Similar example from clojure.core is for example defn itself. Sincerely Meikel -- 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 email to clojure+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/clojure?hl=en
Re: How to start using clojureCLR?
Hi! Thanks for the link. I really appreciate it. It looks like the CLR project is really in it first stage. Is someone working on the tools? Any plans to integrate it with VS? thanks! and thanks for the CLR version! On Thu, Dec 29, 2011 at 2:04 PM, Benny Tsai wrote: > Hi Erlis, > > This is the most recent blog entry I've found w.r.t. getting up and > running with Clojure CLR: > > > http://www.myclojureadventure.com/2011/10/getting-started-with-clojure-clr.html > > What I really like about this particular blog is that the author has also > written follow-up articles (in Nov. and Dec. of 2011) on how to do things > like talk to SQL Server from Clojure CLR and how to call into Clojure CLR > from C#. Hope this helps! > > > On Tuesday, December 27, 2011 9:59:09 AM UTC-8, Erlis Vidal wrote: >> >> Hi group, >> >> I just joined the group and I'm really hypnotized with the Clojure >> language. Most of the time in my day job I do .Net development but outside >> of the job I'm always trying to learn and apply other languages and >> technologies. The curse of the mainstream. >> >> I've just finished Stuart's book "Programming Clojure" and I would like >> to start introducing some fun in my day to day programming, and when I saw >> ClojureCLR I was really happy. >> >> The point is that I don't know where to start, I haven't found anything >> that explain how to start working with it. Any blog on how to prepare the >> environment and start using introducing clojure on my .Net projects ? >> >> I'm also curious about ClojureScript, I've been looking CoffeeScript and >> there are some tools that even integrate with Visual Studio allowing to >> generate the JavaScript file associate with the CoffeeScript, is there >> anything like that for ClojureScript? Is it recommended to use >> ClojureScript in the same scenarios as CoffeeScript or they should serve >> different purposes? >> >> I probably should have two questions, but I see so many opportunities to >> use Clojure right now that I don't want to miss anything. >> >> Thanks in advance and let me know where can I find some information, even >> if you feel is irrelevant maybe for me is a gold mine. >> Erlis >> > -- > 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 email to > clojure+unsubscr...@googlegroups.com > For more options, visit this group at > http://groups.google.com/group/clojure?hl=en -- 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 email to clojure+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/clojure?hl=en
Re: How to start using clojureCLR?
Hi Erlis, This is the most recent blog entry I've found w.r.t. getting up and running with Clojure CLR: http://www.myclojureadventure.com/2011/10/getting-started-with-clojure-clr.html What I really like about this particular blog is that the author has also written follow-up articles (in Nov. and Dec. of 2011) on how to do things like talk to SQL Server from Clojure CLR and how to call into Clojure CLR from C#. Hope this helps! On Tuesday, December 27, 2011 9:59:09 AM UTC-8, Erlis Vidal wrote: > > Hi group, > > I just joined the group and I'm really hypnotized with the Clojure > language. Most of the time in my day job I do .Net development but outside > of the job I'm always trying to learn and apply other languages and > technologies. The curse of the mainstream. > > I've just finished Stuart's book "Programming Clojure" and I would like > to start introducing some fun in my day to day programming, and when I saw > ClojureCLR I was really happy. > > The point is that I don't know where to start, I haven't found anything > that explain how to start working with it. Any blog on how to prepare the > environment and start using introducing clojure on my .Net projects ? > > I'm also curious about ClojureScript, I've been looking CoffeeScript and > there are some tools that even integrate with Visual Studio allowing to > generate the JavaScript file associate with the CoffeeScript, is there > anything like that for ClojureScript? Is it recommended to use > ClojureScript in the same scenarios as CoffeeScript or they should serve > different purposes? > > I probably should have two questions, but I see so many opportunities to > use Clojure right now that I don't want to miss anything. > > Thanks in advance and let me know where can I find some information, even > if you feel is irrelevant maybe for me is a gold mine. > Erlis > -- 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 email to clojure+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/clojure?hl=en
:arglists question
Came across the following in one of the clojure libs (congomongo to be
exact)
https://github.com/aboekhoff/congomongo/blob/master/src/somnium/congomongo.clj:464
(defn command
"Executes a database command."
{:arglists '([cmd {:options nil :from :clojure :to :clojure}])}
[cmd & {:keys [options from to]
:or {options nil from :clojure to :clojure}}]
(let [db (get-db *mongo-config*)
coerced (coerce cmd [from :mongo])]
(coerce (if options
(.command db ^DBObject coerced (int options))
(.command db ^DBObject coerced))
[:mongo to])))
My question is why do we have BOTH :arglists metadata and usual fn
args destructuring?
{:arglists '([cmd {:options nil :from :clojure :to :clojure}])}
[cmd & {:keys [options from to]
:or {options nil from :clojure to :clojure}}]
--
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 email to
clojure+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/clojure?hl=en
[ANN] s3-wagon-private
One common problem when developing closed-source Clojure applications is finding a good place to store private dependencies. Up until now the recommended method was to run your own Archiva or Nexus server, which involves more moving parts than most people rightly want to bother with. Last week I implemented a way to easily deploy private artifacts to S3: https://github.com/technomancy/s3-wagon-private It doesn't have the proxying advantages of Archiva/Nexus, but it's several orders of magnitude simpler. You just add a :repositories entry with a URL beginning with "s3p://" and add your credentials to ~/.lein/init.clj, and then you can deploy to and consume from it easily. Give it a try and let me know how it works for you. -Phil -- 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 email to clojure+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/clojure?hl=en
Re: Clojure list syntax sugar: f(x) notation
do you mean syntax sugar = macro ?
On Thu, Dec 29, 2011 at 12:48 PM, James Reeves wrote:
> On 29 December 2011 16:35, Louis Yu Lu wrote:
> > Agree on looking from the angle of data structure and their internal
> > presentation. But conceptually, [] and {} are just syntax sugars:
> > [x y] -> (vector x y)
> > {x y} -> (hash-map x y)
> > #{x y} -> (hash-set x y)
>
> Well, no, not really.
>
> It's true that (vector x y) evaluates to [x y], but that's not syntax
> sugar, any more than (+ 1 1) is syntax sugar for 2.
>
> - James
>
> --
> 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 email to
> clojure+unsubscr...@googlegroups.com
> For more options, visit this group at
> http://groups.google.com/group/clojure?hl=en
>
--
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 email to
clojure+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/clojure?hl=en
Re: Clojure list syntax sugar: f(x) notation
On 29 December 2011 16:35, Louis Yu Lu wrote:
> Agree on looking from the angle of data structure and their internal
> presentation. But conceptually, [] and {} are just syntax sugars:
> [x y] -> (vector x y)
> {x y} -> (hash-map x y)
> #{x y} -> (hash-set x y)
Well, no, not really.
It's true that (vector x y) evaluates to [x y], but that's not syntax
sugar, any more than (+ 1 1) is syntax sugar for 2.
- James
--
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 email to
clojure+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/clojure?hl=en
Re: Clojure list syntax sugar: f(x) notation
Why not create a klingon version ?
> How about using a and b instead of ( ) so we could have faab which would be
> the equivalent of (f a) so it would rule out symbolnames with an a in any
> place but the first it, also we could go for less used characters as I don't
> know ¥ and µ for example so that would not be half as fun I think.
> --
> Heinz N. Gies
> he...@licenser.net
> http://licenser.net
> > On Dec 29, 2011, at 18:03, Mark Rathwell wrote:
> > > The thing about lisps, though, is that code and data are represented
> > with the same structure. Adding sugar that makes them appear to be
> > different things would not help anyone, especially the beginner. It
> > will make grasping macros, among other things, much more difficult
> > down the road. Getting used to the syntax is, for practical reasons,
> > a necessary, and short, process, and giving new users a way to bypass
> > that would hurt more than it helps. (Not to mention the effect on
> > experienced users of having to now deal with this additional syntax in
> > code in the wild.)
> > > > That said, don't let me stop you from having fun and learning with
> > this little experiment ;)
> > > > On Thu, Dec 29, 2011 at 11:35 AM, Louis Yu Lu
> > > > wrote:
> >> Agree on looking from the angle of data structure and their internal
> >> presentation. But conceptually, [] and {} are just syntax sugars:
> >> [x y] -> (vector x y)
> >> {x y} -> (hash-map x y)
> >> #{x y} -> (hash-set x y)
> >> The 2 element structures are all become 3 element lists.
> >> > >> Louis
> >> > >> On Dec 29, 7:03 am, James Reeves wrote:
> >>> On 29 December 2011 04:49, Louis Yu Lu wrote:
> >>> > Instead of using overloaded (), may be f[x] will cause less
> >>> > trouble,
> and more inline with clojure's syntax as [ ] already being used for
> defining the arguments of the function.
> >>> > >>> I think you need to look at this from a slightly different angle.
> >>> > >>> In Clojure, as in all Lisps, code is represented by data structures
--
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 email to
clojure+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/clojure?hl=en
Re: Interested in a port of Ruby's String#unpack
I think I fixed the take-ulong problem, and I've pushed 0.2.0 to clojars. Let me know if you have any problems with it. - Geoff On Dec 27, 12:47 pm, Geoff Salmon wrote: > I've pushed some updates to get it running with 1.3. take-ulong is > still broken because clojure.lang.BigInt doesn't seem to support bit- > and, but if you don't need that, give it a shot. > > On Dec 27, 9:11 am, mrb_bk wrote: > > > > > > > > > This looks great, take-ubyte is basically exactly what I needed. I'll > > let you know if it works when I try it out this afternoon -- not sure > > what kind of work needs to be done to bring it up to date. > > > On Dec 27, 1:03 am, Geoff Salmon wrote: > > > > Hi, does the unpack function in this library do what you're looking > > > for?https://github.com/geoffsalmon/bytebuffer > > > It unpacks values from Java's ByteBuffer objects instead of strings, > > > which seemed more appropriate in Java-land. > > > > I haven't touched the code since Clojure 1.2, but if it looks useful I > > > can try to bring it up to date. > > > > - Geoff > > > > On Dec 26, 10:03 pm, mrb_bk wrote: > > > > > I also thought I would mention that I've been hanging out in #clojure > > > > as mrb_bk - please hit me up if you would like to chat about this. > > > > > On Dec 26, 10:08 am, mrb_bk wrote: > > > > > > Hey Everyone: > > > > > > I'm working on a project in Clojure that involves parsing binary data > > > > > files. Specifically, I'm building a tool for analyzing Redis (http:// > > > > > redis.io) dump files (.rdb format). The very beginnings of this > > > > > nascent project are here:http://github.com/mrb/pianist. I am a > > > > > beginner to Clojure and Lisp in general, but I'm a long time Ruby > > > > > programmer with experience in C, Java, etc. During the course of > > > > > working through some Clojure learning materials and general poking > > > > > around the web and #clojure in IRC, I've noticed that one of my > > > > > favorite tools for working with binary data from Ruby is missing in > > > > > the Java/Clojure world. This is String#unpack: > > > > > >http://www.ruby-doc.org/core-1.9.3/String.html#method-i-unpack > > > > > > After a brief Twitter conversation with @abedra, and while I get the > > > > > chance to submit my contributors agreement in order to access Clojure- > > > > > dev, I thought I'd bring this topic up here. > > > > > > For what it's worth, I've checked out Gloss, which is interesting but > > > > > a bit too opinionated for me. Plus I believe that something to this > > > > > effect should be part of clojure core - it seems that easy interface > > > > > for lazily handling binary data as seqs doesn't exist as such right > > > > > now. > > > > > > If anyone has comments on the beginnings of my codebase (be gentle), > > > > > or thoughts about implementing something similar to String#unpack, or > > > > > a suggestion of an alternative set of tools I could use, that would be > > > > > great. Thanks! > > > > > > Mike > > > > > twitter.com/mrb_bk > > > > > github.com/mrb -- 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 email to clojure+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/clojure?hl=en
Re: Clojure list syntax sugar: f(x) notation
How about using a and b instead of ( ) so we could have faab which would be the
equivalent of (f a) so it would rule out symbolnames with an a in any place but
the first it, also we could go for less used characters as I don't know ¥ and µ
for example so that would not be half as fun I think.
--
Heinz N. Gies
he...@licenser.net
http://licenser.net
On Dec 29, 2011, at 18:03, Mark Rathwell wrote:
> The thing about lisps, though, is that code and data are represented
> with the same structure. Adding sugar that makes them appear to be
> different things would not help anyone, especially the beginner. It
> will make grasping macros, among other things, much more difficult
> down the road. Getting used to the syntax is, for practical reasons,
> a necessary, and short, process, and giving new users a way to bypass
> that would hurt more than it helps. (Not to mention the effect on
> experienced users of having to now deal with this additional syntax in
> code in the wild.)
>
> That said, don't let me stop you from having fun and learning with
> this little experiment ;)
>
> On Thu, Dec 29, 2011 at 11:35 AM, Louis Yu Lu wrote:
>> Agree on looking from the angle of data structure and their internal
>> presentation. But conceptually, [] and {} are just syntax sugars:
>> [x y] -> (vector x y)
>> {x y} -> (hash-map x y)
>> #{x y} -> (hash-set x y)
>> The 2 element structures are all become 3 element lists.
>>
>> Louis
>>
>> On Dec 29, 7:03 am, James Reeves wrote:
>>> On 29 December 2011 04:49, Louis Yu Lu wrote:
>>>
Instead of using overloaded (), may be f[x] will cause less trouble,
and more inline with clojure's syntax as [ ] already being used for
defining the arguments of the function.
>>>
>>> I think you need to look at this from a slightly different angle.
>>>
>>> In Clojure, as in all Lisps, code is represented by data structures.
>>> In Clojure, (x y) is a linked list of two elements, [x y] is a vector,
>>> and {x y} a map. You need to think about Clojure code in terms of the
>>> data structures beneath.
>>>
>>> So you're proposing that x[y] be considered a two-element list. This
>>> is an unusual syntax for defining a list in any language I know, and
>>> looks confusingly similar to a single element followed by a vector.
>>>
>>> Try not to ask the question, "What syntax is good for representing a
>>> function call?" and instead ask, "What syntax is good for representing
>>> a linked list of elements?"
>>>
>>> - James
>>
>> --
>> 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 email to
>> clojure+unsubscr...@googlegroups.com
>> For more options, visit this group at
>> http://groups.google.com/group/clojure?hl=en
>
> --
> 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 email to
> clojure+unsubscr...@googlegroups.com
> For more options, visit this group at
> http://groups.google.com/group/clojure?hl=en
--
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 email to
clojure+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/clojure?hl=en
Re: Clojure list syntax sugar: f(x) notation
The thing about lisps, though, is that code and data are represented
with the same structure. Adding sugar that makes them appear to be
different things would not help anyone, especially the beginner. It
will make grasping macros, among other things, much more difficult
down the road. Getting used to the syntax is, for practical reasons,
a necessary, and short, process, and giving new users a way to bypass
that would hurt more than it helps. (Not to mention the effect on
experienced users of having to now deal with this additional syntax in
code in the wild.)
That said, don't let me stop you from having fun and learning with
this little experiment ;)
On Thu, Dec 29, 2011 at 11:35 AM, Louis Yu Lu wrote:
> Agree on looking from the angle of data structure and their internal
> presentation. But conceptually, [] and {} are just syntax sugars:
> [x y] -> (vector x y)
> {x y} -> (hash-map x y)
> #{x y} -> (hash-set x y)
> The 2 element structures are all become 3 element lists.
>
> Louis
>
> On Dec 29, 7:03 am, James Reeves wrote:
>> On 29 December 2011 04:49, Louis Yu Lu wrote:
>>
>> > Instead of using overloaded (), may be f[x] will cause less trouble,
>> > and more inline with clojure's syntax as [ ] already being used for
>> > defining the arguments of the function.
>>
>> I think you need to look at this from a slightly different angle.
>>
>> In Clojure, as in all Lisps, code is represented by data structures.
>> In Clojure, (x y) is a linked list of two elements, [x y] is a vector,
>> and {x y} a map. You need to think about Clojure code in terms of the
>> data structures beneath.
>>
>> So you're proposing that x[y] be considered a two-element list. This
>> is an unusual syntax for defining a list in any language I know, and
>> looks confusingly similar to a single element followed by a vector.
>>
>> Try not to ask the question, "What syntax is good for representing a
>> function call?" and instead ask, "What syntax is good for representing
>> a linked list of elements?"
>>
>> - James
>
> --
> 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 email to
> clojure+unsubscr...@googlegroups.com
> For more options, visit this group at
> http://groups.google.com/group/clojure?hl=en
--
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 email to
clojure+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/clojure?hl=en
Re: Clojure list syntax sugar: f(x) notation
Agree on looking from the angle of data structure and their internal
presentation. But conceptually, [] and {} are just syntax sugars:
[x y] -> (vector x y)
{x y} -> (hash-map x y)
#{x y} -> (hash-set x y)
The 2 element structures are all become 3 element lists.
Louis
On Dec 29, 7:03 am, James Reeves wrote:
> On 29 December 2011 04:49, Louis Yu Lu wrote:
>
> > Instead of using overloaded (), may be f[x] will cause less trouble,
> > and more inline with clojure's syntax as [ ] already being used for
> > defining the arguments of the function.
>
> I think you need to look at this from a slightly different angle.
>
> In Clojure, as in all Lisps, code is represented by data structures.
> In Clojure, (x y) is a linked list of two elements, [x y] is a vector,
> and {x y} a map. You need to think about Clojure code in terms of the
> data structures beneath.
>
> So you're proposing that x[y] be considered a two-element list. This
> is an unusual syntax for defining a list in any language I know, and
> looks confusingly similar to a single element followed by a vector.
>
> Try not to ask the question, "What syntax is good for representing a
> function call?" and instead ask, "What syntax is good for representing
> a linked list of elements?"
>
> - James
--
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 email to
clojure+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/clojure?hl=en
Re: about partial and clojure curry
Sorry if this has already been addressed... I can understand both Ron's pain and the reasoning why it's not possible to have Haskell style currying; however, I wonder if there's a compromise possible. Right now, we: (map #(+ 3 %) [1 2 3] or (map (partial + 3) [1 2 3]) The (partial + 3) is a bit too verbose for me, and I can define my one partial fn if I want. (def % partial) (map (% + 3) [1 2 3]) That works, and I do prefer it, but I think I'd rather have (map %(+ 3) [1 2 3]) This solution feels like a shorthand for #(... %), but it also feels familiar because I'm putting the % before for parenthesis. Unfortunately, I have no idea what the impact of adding another reader macro would be, so maybe this is an unrealistic solution. I'd be interested to hear feedback. Cheers, Jay -- 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 email to clojure+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/clojure?hl=en
Re: Clojure list syntax sugar: f(x) notation
On 29 December 2011 04:49, Louis Yu Lu wrote:
> Instead of using overloaded (), may be f[x] will cause less trouble,
> and more inline with clojure's syntax as [ ] already being used for
> defining the arguments of the function.
I think you need to look at this from a slightly different angle.
In Clojure, as in all Lisps, code is represented by data structures.
In Clojure, (x y) is a linked list of two elements, [x y] is a vector,
and {x y} a map. You need to think about Clojure code in terms of the
data structures beneath.
So you're proposing that x[y] be considered a two-element list. This
is an unusual syntax for defining a list in any language I know, and
looks confusingly similar to a single element followed by a vector.
Try not to ask the question, "What syntax is good for representing a
function call?" and instead ask, "What syntax is good for representing
a linked list of elements?"
- James
--
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 email to
clojure+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/clojure?hl=en
Re: [ANN] swank-clojure 1.3.4 released
On Thu, Dec 29, 2011 at 3:07 AM, Phil Hagelberg wrote: >> On Wed, Dec 28, 2011 at 6:33 AM, Phil Hagelberg wrote: >>> I just pushed out version 1.3.4 of Swank Clojure. >> >> Does it work with Clojure 1.2? What exclusions do I need for that in >> my project.clj? > > I'm not aware of any issues with using Swank Clojure in 1.2. If you're > having trouble please post details. It does work fine on 1.2.1 with the aforementioned exclusion for ring. However, I don't see the colored stacktraces yet. Does that need any extra config? I am starting the swank server externally using `lein swank`. It doesn't work even when I `jack-in` from Emacs. Regards, BG -- Baishampayan Ghose b.ghose at gmail.com -- 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 email to clojure+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/clojure?hl=en
