All,
The London Clojurians are hosting a hackday to work on their community
website (http://londonclojurians.org) on Saturday 16th June 10:00-16:00 BST.
All welcome, details here:
http://ldncljweb-june2012.eventbrite.com/
Hope to see you there!
- Dale
--
You received this message
in the past:
http://www.javamex.com/tutorials/memory/instrumentation.shtml
You'd need to walk the object tree and sum up the results avoiding
cycles.
many thanks,
- Dale Thatcher
--
You received this message because you are subscribed to the Google
Groups Clojure group.
To post
This statement is ironic, considering the definition of a functional
closure, after which Clojure is presumably named.
You're missing the point. A defn inside another defn doesn't do what you
think it does. defn always creates a global variable, even when it looks
like it should create a
When speaking about general TCO, we are not just talking about
recursive self-calls, but also tail calls to other functions. Full TCO
in the latter case is not possible on the JVM at present whilst
preserving Java calling conventions (i.e without interpreting or
inserting a trampoline etc).
On Aug 2, 11:07 pm, Mark Engelberg mark.engelb...@gmail.com wrote:
Can you distill this down to the smallest possible example that demonstrates
the error?
Nope. Just spent some time trying to duplicate the nested function bug
in a simpler context.
A pointer to the place where I should deposit
On Aug 3, 11:26 am, Moritz Ulrich ulrich.mor...@googlemail.com
wrote:
Defining function (with defn) inside another function isn't very
beautiful (def* outside of the top-level is generally disregarded). It
looks like you use thhelp only inside the thsolve-function. Use either
letfn or (let
values at
run time. There is no error indicator, but the values are wrong.
These are in 1.1, and the first problem is in the current beta of 1.2.
Not sure where I should post this.
Dale
; Clojure solution to nqueens benchmark.
; D. Parson, Summer 2010.
; See threadlim_nqueens.java for more details
The JVM has an unconditional goto opcode and the ability to re-bind
function parameters, so why no tail-call optimization? Thanks.
Dale
--
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
