Ilya, I have checked in a unit test for the tasklist example that demonstrates it working correctly locally. Can you try it and see what's different for you?
Git repos: http://github.com/stuarthalloway/programming-clojure/tree/master Then "bin/runtests.sh" or "bin\runtests.bat" depending on your platform. The individual test is examples/test/tasklist.clj. Thanks, Stu > Hi, Stuart. > > I would like to be able to demo the sample code from the book in IDEA > > That's great, I'm really happy to hear it. > > As for all three issues you've mentioned, all of them have same > origin and related to so-called evaluator API. What you can see now > using debugger is nothing but vanilla Java stack, some of whose > variable may coincide with appropriate Clojure variables. > Implmentation of watches, evaluate expression or some specific cases > like dealing with lazy structures is _very_ non-trivial problem, > cause all clojure constructs, written, say, in 'watches' section > should be translated to correct Java code to capture appropriate > stack and environment from JVM and being evaluated. > For now, we solved this problem partially for Groovy, because Groovy > is not so hard to translate to Java and we're working on the same > problem for Scala, which is much more dificult because of presence > of string typeing. As for Clojure, I don't see an easy way for now > to implement such feature. > For me such tasks as smart completion and resolve have greater > priority. > > BTW, I'm not sure, that thiss issue was already mentioned in errata > for book, but I failed to compile tasklist.clj example from last > book version (27 feb), because some function (sort of `lazy-eval') > from clojure-contrib raised an error during compilation. Same result > was obtained by compilation from command line, so I'm afraid some- > thing wrong either with current clojure-contrib version or this > example. > > Kind regards, > Ilya > > > > > 2009/3/25 Stuart Halloway <stuart.hallo...@gmail.com> > > Hi Ilya, > > I would like to be able to demo the sample code from the book in IDEA. > Here are a few things I am seeing so far: > > (1) When I set a breakpoint, I get a warning icon that says "no > executable code found at..." but the breakpoint does in fact seem to > work. > > (2) The variable window correctly displays collections, but not large/ > infinite sequences. If you try to open a variable view on an infinite > sequence, it will use all of memory. Can the plugin be modified to > respect the *print-length* and *print-depth* variables? > > (3) I am unable to set a watch on the special variable *print-length*. > The entry UI goes wonky when I reach the hyphen character in the name. > > It's exciting to see the plugin moving forward, thanks for your > efforts! > > Best, > Stu > > > Hello, all. > > > > I've just uploaded new version of La Clojure plugin for IntelliJ > > IDEA. Among several bugfixes and minor changes I have to note > > several essential moments. > > > > 1. Now Clojure support is added as so-called `facet', which may be > > attached to every module. Creating new module, just choose Clojure > > among desired technologies. In this case necessary clojure jar will > > be downloaded automatically and adjusted as a project library unless > > you point to it manually. > > > > 2. If you open existing project, clojure facet will be detected > > automatically. For now facet serves as a label for clojure-aware > > modules. In that modules you may invoke "create new clojure file" > > action and their clojure files will be compiled. > > > > 3. From now IntelliJ IDEA provides support for batch compilation of > > Clojure files, whose namespace is marked by :gen-calss tag. Compiled > > classes will be places to the appropriate output directory of a > > module. One may choose, which sources should be compiled first - > > Java or Clojure to resolve one-way dependencies. By default Clojure > > is compiled first. Moreoverm you may to choose whether to copy *.clj > > files to output path or not (this might be useful if you're going to > > invoke some functions from *.clj files dynamically). And, of course, > > automatic detection and compilation of class-labeled clojure files > > may be switched off. For more details see File -> Settings -> > > Compiler -> Clojure. > > > > For someone these settings might seem not sufficiently flexible. So, > > all comments and proposals are appreciated. :) > > > > With best regards, > > Ilya Sergey > > > > > > > > > > > > > > > > --~--~---------~--~----~------------~-------~--~----~ 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 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 -~----------~----~----~----~------~----~------~--~---
