Re: GSoC Report: CinC, port of the clojure compiler in clojure

Congratulations Nicola, and thanks for all the hard work - this is a great project! On 23 September 2013 14:26, Ambrose Bonnaire-Sergeant < abonnaireserge...@gmail.com> wrote: > Excellent work! To hear CinC is a long term project is music to my ears! > > Ambrose > > > On Mon, Sep 23, 2013 at 4:5

Re: ANN How to Write a Useful Change Log

I'm a little late to the party here, but I just wanted to thank you guys for writing these posts - they're great. Thanks for emphasizing the social aspects of software development, this is all to often forgotten. On 13 September 2013 09:09, Michael Klishin wrote: > The ClojureWerkz team recently

Re: Stretch Goal 1: CinC development

This is fantastic news. If anything, CinC is almost a more important project since its applications are so broad. I'm delighted to see the community getting behind both of these projects - congratulations Ambrose and Nicola! On 1 October 2013 07:02, Rich Morin wrote: > I am delighted that the c

[ANN] Public Early Access Program for Cursive, the IntelliJ-based Clojure IDE

Hi everyone, Following on from the discussion a while back about interest in a commercial Clojure IDE, I'm pleased to announce the public Early Access Program for Cursive (http://cursiveclojure.com). Cursive is based on the IntelliJ platform and is mostly written in Clojure. The website is still a

Re: [ANN] Public Early Access Program for Cursive, the IntelliJ-based Clojure IDE

Hi Vjeran, Thanks! I'm glad you're liking it. The namespace in the current REPL is displayed at the top of the window, in the REPL tab name. Cheers, Colin On 9 October 2013 07:52, wrote: > Congratulations! > > EAP looks promising - its already much better than La Clojure. I don't > know if th

Re: Teaching Clojure to students (how ?)

Right, there should be no problem doing this - pretty much all the editors/IDEs out there start an external process for the REPL server, and it should be able to use any Clojure version you like, independently of the version used by the IDE itself. On 9 October 2013 08:21, Cedric Greevey wrote:

Re: [ANN] Public Early Access Program for Cursive, the IntelliJ-based Clojure IDE

; > -Vjeran > > > On Tuesday, October 8, 2013 11:10:33 PM UTC+2, Colin Fleming wrote: > >> Hi Vjeran, >> >> Thanks! I'm glad you're liking it. The namespace in the current REPL is >> displayed at the top of the window, in the REPL tab name. >> &

Re: Clojure can't import some Java classes

Yup, it's true. I suffer from this as well. When I'm compiling Cursive normal compilation fails because a bunch of the IntelliJ classes assume the IntelliJ platform is running and barf if it's not. I have an awful hack which is to run the compilation within their test framework which sets up a mock

Re: Clojure can't import some Java classes

also it's a quite laborious and brittle solution since updates to the > real classes would break the mock classes. Definitely interested in ideas > others may have. > > > On Saturday, October 12, 2013 4:36:31 AM UTC-4, Colin Fleming wrote: > >> Yup, it's true.

Re: Clojure can't import some Java classes

I've also had a lot of problems with def'ed forms. For example, if I do this: (def no-spacing (Spacing/createSpacing 0 0 0 false 0)) Which looks like this: public static Spacing createSpacing(int minSpaces, int maxSpaces,

Re: Clojure can't import some Java classes

en you shouldn't do this in a def. > > > On Wednesday, October 23, 2013 9:01:15 AM UTC-5, Aaron Cohen wrote: > >> I'm not sure if this is related to the original problem. >> >> How is the setFactory method expected to be invoked, through some sort >> of

Re: [ANN] collection-check: validation for data structure variants

This looks like a really useful library, but I mostly came here to say +1 for the use of "lacunae". Now I have to find a way to insert that into my own conversations. On 31 October 2013 15:13, Zach Tellman wrote: > It's relatively rare that people write variants of Clojure data > structures.

Re: Cursive IntelliJ working on multiple Leiningen projects & require - refer :as not working

Right, this is still a little messy - this is actually something I'll be working on this week. I fixed up the existing support which wouldn't allow multiple modules at all (or at least would throw exceptions when Aether couldn't resolve the dependencies), but it's still not smart about adding one m

Re: Cursive IntelliJ working on multiple Leiningen projects & require - refer :as not working

to the other and is basically manually doing what any future support will do automatically. That link will also survive a project refresh. On 2 November 2013 10:06, Colin Fleming wrote: > Right, this is still a little messy - this is actually something I'll be > working on this week.

Re: Cursive IntelliJ working on multiple Leiningen projects & require - refer :as not working

Hi Niels, I've just released Cursive 0.1.05 which fixes this issue. Documentation for the Leiningen support is here. Basically you should be able to just import your project wholesale and it will automatically work out all the dependencies. Check

Re: Cursive IntelliJ working on multiple Leiningen projects & require - refer :as not working

e checkout project(s). > > > On Tuesday, November 5, 2013 7:51:00 AM UTC+1, Colin Fleming wrote: > >> Hi Niels, >> >> I've just released Cursive 0.1.05 which fixes this issue. Documentation >> for the Leiningen support is >> here<http://cursivec

Re: Cursive IntelliJ working on multiple Leiningen projects & require - refer :as not working

Module ''. That will copy your Clojure files to the output path and they'll be picked up by the REPL then. On 6 November 2013 10:50, Colin Fleming wrote: > Hmm, there may be some problem with the classpath there - I'll take a look. > > > On 5 November 2013

Re: Step by step debugging

I'm slightly late to the discussion, sorry - currently moving cities. Cursive does indeed have a stepping debugger which works well with Clojure, although it's quite slow (I haven't been able to figure out why, yet - I suspect Clojure adds a lot of line information to the bytecode). There have also

Re: Step by step debugging

the body of the > expression. > > > On Fri, Nov 8, 2013 at 12:24 AM, Colin Fleming < > colin.mailingl...@gmail.com> wrote: > >> I'm slightly late to the discussion, sorry - currently moving cities. >> Cursive does indeed have a stepping debugger which works well with

Re: Step by step debugging

One quick clarification about -Dclojure.compile.disable-locals-clearing=true which bit me - this is actually read in clojure.main, which uses it to initialise the *compiler-options* var. This means that if you start your app in any other way (I'm not sure if lein duplicates the clojure.main functio

Re: Step by step debugging

lem line in your source code, for example if > (default) threw a ClassCastException because "default" did not implement > IFn in the above the stacktrace might point to line 8 when it was really > line 5 of your (cond ...) expression (but line 8 of the (if ...) it > macroexpand

Re: Step by step debugging

t; application. The code had gotten too convoluted; parts of it are very old, >> with many layers of accretions. I've been doing the rewrite in Clojure as >> my first Clojure project. I'm seriously wondering at this moment, though, >> whether I should stop and do the r

Re: Regarding Clojure's license

At least one company (mine at the time) had a problem with using LGPL software because of the clause where you explicitly allow reverse engineering of your product in order to use a different version of the LGPL library. That's enough to give any corporate lawyer the screaming heebie jeebies, not t

Re: Step by step debugging

"Done!" > (yo (dec n) > > with *compiler-options* set to {:disable-locals-clearing true}, is there a > way to see, after the exception is thrown, that n had the value 15? > > Thanks- > > Marshall > > > On Wednesday, November 13, 2013 3:45:27

Re: Regarding Clojure's license

rary ever made that cut. On 14 November 2013 16:46, John Gabriele wrote: > On Wednesday, November 13, 2013 6:06:02 PM UTC-5, Colin Fleming wrote: > > > > I don't see why a company would have any problem at all with *using* > > > LGPL'd software, even in a

Re: [ANN] overload-middleware 0.1.1

> > Web browsers don't "pick a random sleep time before trying again", though; > they display a 500 error page and the user promptly clicks "reload" while > making an exasperated sigh. > That sounds like "picking a random sleep time before trying again" to me :-) > If the client is something ot

Re: [ANN] Clojure 1.6.0-alpha3

BTW (and I may be a little late here) - is there a plan to add keyword creation to the API? Keywords are a pretty common part of many Clojure APIs, it would be good to allow their creation without forcing people to use Keyword.intern(). On November 23, 2013 at 8:16:48 PM, a...@puredanger.com (a.

Re: [ANN] introduction to opencv development with clojure

Congratulations Mimmo, that's great news. I'd like to play with OpenCV at some point, I'll definitely use this if/when I do. And yes, I totally agree - Seesaw is the gold standard with lib wrapping IMO, it's a fantastic piece of work. Cheers, Colin On 12 December 2013 08:00, Mimmo Cosenza wrote

Re: [ANN] introduction to opencv development with clojure

12, 2013, at 4:01 AM, Colin Fleming > wrote: > > > Seesaw is the gold standard with lib wrapping IMO, it's a fantastic > piece of work. > > thanks. I'll start to study it today and try to grab idea from there. if > anyone have any suggestion on best-practices to w

Re: Clojure can't import some Java classes

I've just spent some time today looking at the compiler code, and unfortunately I think the answer is "no". When a symbol is imported, Clojure currently instantiates the Class object using Class.forName() and stores that in the namespace's mapping. At the point the Class is instantiated, static ini

Re: get rid of reflection in proxy-super?

I actually just wrote a long reply detailing how to type hint 'this', and then noticed that you've already done that! This exact case (paintComponent) is the one reflection warning I can't get rid of in the whole Cursive codebase, I can't figure it out either. On 23 December 2013 01:03, Jim - Foo

Re: get rid of reflection in proxy-super?

cted. I never found a workaround. > > Dave > > > On Sunday, December 22, 2013, Colin Fleming wrote: > >> I actually just wrote a long reply detailing how to type hint 'this', and >> then noticed that you've already done that! This exact case >> (paintCom

Re: get rid of reflection in proxy-super?

ould be in a finally block. Currently if the superclass method throws an exception, the proxy will be left with the superclass call in its proxy mappings. On 23 December 2013 16:41, Colin Fleming wrote: > But surely proxy-super should be designed to call protected methods? I'd > have to c

Re: Implementation options for auto-complete and symbol resolution while coding

As another data point, Cursive's symbol resolution in normal code editing is totally static - it doesn't use the REPL at all. When typing in the REPL window, local resolution is used for the code in the editor and the REPL is used for everything else, so that local symbols can be completed and so f

Re: get rid of reflection in proxy-super?

That is indeed the same issue, and it even includes a patch with a test! I've voted for this one, please consider doing the same if this issue has caught you. Link: http://dev.clojure.org/jira/browse/CLJ-983 On 25 December 2013 13:22, Matching Socks wrote: > (Re Colin's note that a proxy gets d

Re: get rid of reflection in proxy-super?

original binding on exception... > > Jim > > > > On 25/12/13 04:06, Colin Fleming wrote: > > That is indeed the same issue, and it even includes a patch with a test! > I've voted for this one, please consider doing the same if this issue has > caught you. Link: htt

Re: get rid of reflection in proxy-super?

per call in the method body and not in the fn that the rest of > the proxy body goes into, which will avoid IllegalAccessError but make it > so that on-the-fly modification of the proxy can't change the proxy-super > part). > > > On Wed, Dec 25, 2013 at 3:04 PM, Colin Flemin

Re: Clojure can't import some Java classes

mpilation, at least. I'll report back if I ever get it working. On 15 December 2013 14:05, Colin Fleming wrote: > I've just spent some time today looking at the compiler code, and > unfortunately I think the answer is "no". When a symbol is imported, > Clojure curre

Re: get rid of reflection in proxy-super?

given the requirement to modify the compiler anyway, I'd go straight for a more sane extend-class form. On 27 December 2013 17:49, Cedric Greevey wrote: > On Thu, Dec 26, 2013 at 6:57 PM, Colin Fleming < > colin.mailingl...@gmail.com> wrote: > >> The problem is that your

Re: Clojure can't import some Java classes

ach Oakes wrote: > >> Yeah I tried this with RoboVM, but there are so many classes that needed >> to be stubbed that it turned into an endless rabbit hole, so I gave up. It >> may be a good solution for those who just have one or two problematic >> classes, though. >>

Re: In your opinion, what's the best, and what's the worst aspects of using Clojure?

I think the error complaints are generally more about the errors when you have something wrong in your code. Things like parsing of ns forms has little to no error checking, and you can get some extremely obscure errors. For example if you (or some tool) places an :import clause ahead of your NS do

Re: Clojure can't import some Java classes

ember 2013 20:24, Zach Oakes wrote: > Definitely exciting to hear that it works. Is this something you could > propose as a patch on the Clojure JIRA? > > > On Friday, December 27, 2013 9:52:04 PM UTC-5, Colin Fleming wrote: > >> Wow, that works! You just saved me an extraordi

Re: In your opinion, what's the best, and what's the worst aspects of using Clojure?

Just out of interest (and I'm not trying to be combative here, I'm genuinely curious) - it seems from many of your posts here that this is a serious pain point for you. Why not just use another lisp? High-performance numeric programming doesn't seem like Clojure's strong point and the error handlin

Re: In your opinion, what's the best, and what's the worst aspects of using Clojure?

On Dec 28, 2013, at 8:51 PM, Colin Fleming wrote: > > Just out of interest (and I'm not trying to be combative here, I'm > genuinely curious) - it seems from many of your posts here that this is a > serious pain point for you. Why not just use another lisp? High-performance &

Re: ClojureScript integration with Emacs/Cider ?

Since Cursive (http://cursiveclojure.com) resolves everything statically from source, ClojureScript completion and navigation works for most symbols. There are still a lot that it doesn't know about since cljs-specific functionality is still pretty low, so js/* symbols have no support, and any func

Re: ClojureScript integration with Emacs/Cider ?

sent in IntelliJ Ultimate. I'm still working out how to handle that but it's definitely on the roadmap. On 8 January 2014 00:26, Alexandru Nedelcu wrote: > On Mon, Jan 6, 2014 at 11:10 PM, Colin Fleming < > colin.mailingl...@gmail.com> wrote: > >> Since Cursive (h

Re: Eastwood lint tools - some Qs

This is an interesting discussion, I've been thinking about some of these problems as I move towards adding inspections in Cursive. arglist parsing is a real problem in Clojure. I'd like to be able to flag invocations of functions with bad arities in the editor, but it's very difficult. Even defn i

Re: Eastwood lint tools - some Qs

ike it would if you attempted to compile such code. > > Andy > > > On Mon, Jan 13, 2014 at 6:57 PM, Colin Fleming < > colin.mailingl...@gmail.com> wrote: > >> This is an interesting discussion, I've been thinking about some of these >> problems as I move to

Re: Eastwood lint tools - some Qs

warnings > > Andy > > > On Mon, Jan 13, 2014 at 10:22 PM, Colin Fleming < > colin.mailingl...@gmail.com> wrote: > >> Interesting - but there must be some sort of magic there since otherwise >> every call to defn would be flagged, since its :arglists implies it

[ANN] New Clojure meetup in Auckland, NZ

Hi everyone, I'm pleased to announce a new Clojure meetup in Auckland, New Zealand. We'll have our first meetup on March 27 - it would be great to see anyone interested there. We'll have some talks on La Clojure, Storm and ClojureScript, it should be a good time. Full details here: http://www.mee

Re: Clojure Style Guide

I agree - I thoroughly enjoyed this. On 30 March 2013 08:45, Alan Thompson wrote: > Hey - Just saw a nice article on this in (def newsletter) . It looks like > quite a good reference on the subject. > > https://github.com/bbatsov/clojure-style-guide

Re: Macros in ClojureScript

Hi Kevin, That message means that Clojure can't find the file containing your macros on the classpath. Looking at it, you appear to have the macro file in your src-cljs directory. I've never used ClojureScript, but maybe that should be in your src directory since it's Clojure and not ClojureScript

Re: keyword bug

This is something I noticed the other day - the reader doc states of keywords "They cannot contain '.' or name classes". Clearly most qualified keywords will contain '.'. On 15 April 2013 18:07, Andy Fingerhut wrote: > The description of legal symbols at http://clojure.org/reader could be > some

Re: Head retention example

I'm pretty sure the implementation of locals clearing is all in Compiler.java, in the LocalsBinding class. See canBeCleared in that class. On 23 April 2013 23:37, xumingmingv wrote: > Michal, do you know any resources/links that introduce the internals of > local-clearing? or The Clojure source

Re: Now *there*'s a machine made for Clojure.

I guess you could go for a middle ground where you run a JVM instance per 8 cores or so, which would minimise your intercommunication but still reduce your GC contention. Of course as soon as (> num-jvms 1) you have to write all the communication and deployment code anyway so it might not be a big

<    1   2   3   4