Re: vs. Erlang

2008-09-17 Thread Rich Hickey
On Sep 16, 8:29 pm, Raoul Duke [EMAIL PROTECTED] wrote: http://lambda-the-ultimate.org/node/2865#comment-42428 maybe an approach which would be a not-very-big-diff-to-Clojure to get distributed computing. --~--~-~--~~~---~--~~ You received this message

Re: vs. Erlang

2008-09-17 Thread Rich Hickey
On Sep 16, 8:29 pm, Raoul Duke [EMAIL PROTECTED] wrote: http://lambda-the-ultimate.org/node/2865#comment-42428 maybe an approach which would be a not-very-big-diff-to-Clojure to get distributed computing. I like the fault streams idea mentioned in the linked-to thesis, and have been

Re: Observations and questions regarding long-running, adaptable, transparent software

2008-09-17 Thread Stuart Sierra
Brief response to: On Sep 16, 11:40 pm, falcon [EMAIL PROTECTED] wrote: I also notice that Clojure has the ability to change programs while they are running; however, I haven't been able to find examples of this. Most Lisps give you this for free, since the compiler is integrated into the

Re: Observations and questions regarding long-running, adaptable, transparent software

2008-09-17 Thread Rich Hickey
On Sep 16, 11:40 pm, falcon [EMAIL PROTECTED] wrote: I work on financial software--the kind that reads streaming data and static data from various sources, transforms these streams through various calculations and possibly decides to send out trades. ... Is there a good solution to the

Re: Improved compiler error messages, part 2

2008-09-17 Thread Rich Hickey
On Sep 17, 1:54 pm, Allen Rohner [EMAIL PROTECTED] wrote: After feedback on my previous compiler error message patch, I've started looking into the problem more. My goal is to have the file and line number printed on every user-visible stack trace. An example of my desired output is:

Re: Improved compiler error messages, part 2

2008-09-17 Thread Allen Rohner
It seems to me you need to distinguish runtime errors from compilation errors. For runtime errors, the file and line numbers are already in the stack trace, as Clojure emits that information in the bytecode. For example, in the above trace:         at

Re: Observations and questions regarding long-running, adaptable, transparent software

2008-09-17 Thread Stuart Sierra
On Sep 17, 12:45 pm, Rich Hickey [EMAIL PROTECTED] wrote: While it is possible to make a globally visible change to a var with def, the only appropriate  scenarios for doing so are to fix a bug, or for scratch vars at the repl. This brings up an idea I had a while back -- what if you wanted

Re: Observations and questions regarding long-running, adaptable, transparent software

2008-09-17 Thread Raoul Duke
It's an interesting idea, and something I tried, but the overhead was too great. i know less than nothing here, of course, but... any way to make the default case of nothing has changed be somehow fast (enough), and only the oh poop things got edited have to go into slow-mo for a second to

Re: Generate exposers for ancestral fields

2008-09-17 Thread Matt Revelle
Posted a patch to traverse the class hierarchy looking for the specified fields, it also verifies that the field is protected. Exceptions are thrown if the field isn't found or is found but not protected. Examples: ___A.java___ package pkg; public class A { private String priv = a

Functional style laziness - deferred execution caught me unawares

2008-09-17 Thread Joubert Nel
I ran into an interesting situation today, and although I have realized my mistake, thought I would share as I think it is a good illustration of a scenario where one may mistakenly rely on expected functional correctness when you don't fully consider the ramifications of lazy sequences and

Re: Serialization Snag

2008-09-17 Thread Joubert Nel
Hello noahr, I have created a library for myself to do persistence in Clojure to Berkeley DB. I generally leverage Clojure's reader support for (de)serialization. However, in one instance I had to implement a particular interface and pass that class as parameter to the Berkeley API. At first