Re: Errors

Very useful. So it is a *bit* philosophical :) I guess the unabashedly hosted philosophy is one I wasn't so sure was intentional but it's good to understand; and embracing that changes the way you'd teach or introduce the language. Gotcha. Where I thought I "had to form" a dual mental model and

Re: Errors

On Tuesday, December 6, 2016 at 5:55:52 AM UTC-6, Paul Walker wrote: > > Wow thank you for the fulsome responses > > A couple of thoughts. I brashly said > > > I cherrypicked a case where the runtime difference would be tiny > > and I appreciate the clarifications - especially that my naive >

Re: Errors

Wow thank you for the fulsome responses A couple of thoughts. I brashly said > I cherrypicked a case where the runtime difference would be tiny and I appreciate the clarifications - especially that my naive add-one-bytecode calculation in my head (the code I pasted has a pretty meaty “analyze”

Re: Errors

On Monday, December 5, 2016 at 10:36:59 PM UTC-6, Sean Corfield wrote: > > Several of the Clojure/core folks have said at various times over the > years that Clojure is deliberately not optimized for novices, on the > grounds that whilst everyone starts out as a novice, most of your time >

Re: Errors

On Monday, December 5, 2016 at 7:28:21 PM UTC-6, p...@pwjw.com wrote: > > Hi! > Hi Paul, > > Boy I really think you've all done a nice job with Clojure. I've used > quite a few environments over the years and clojure + CIDER + etc is a > great experience. The immutability and threading are

Re: Errors

On Tuesday, 6 December 2016 10:47:42 UTC+8, James Reeves wrote: > > On 6 December 2016 at 01:28, wrote: >> >> And the error messages are not good. >> >> So I was wondering: Is this a philosophical thing? Or is it an effort >> thing? And if it is an effort thing, is there some

Re: Errors

> I cherrypicked a case where the runtime difference would be tiny I wouldn’t be so sure of that. Adding any additional code to the function call logic is going to impact almost every single expression in Clojure and that “tiny” difference is going to add up pretty fast. As others have

Re: Errors

Yeah I understand that tradeoff. I cherrypicked a case where the runtime difference would be tiny but others are harder I’m sure. I guess I will go figure out how spec applies to my project. Thanks as always. This group is so responsive. Appreciated. - Paul > On Dec 5, 2016, at 9:46

Re: Errors

On 6 December 2016 at 01:28, wrote: > > And the error messages are not good. > > So I was wondering: Is this a philosophical thing? Or is it an effort > thing? And if it is an effort thing, is there some sort of plan for what > effort to put in? And if so, can I help by closing

Re: Errors

I think it has been rehashed often and core is very conservative about changes, but the current latest and greatest for improving many kinds of errors is going to be clojure.spec, which runs parallel to the actual execution path, so as not to effect things like performance or old code that depends

Re: Errors w/ dynamic symbols in macro-utils or monads?

Does this still happen for you? It appears to still be the case in my environment. Dropping back to Clojure *1.2.1* seems to work but in addition to trying out monads, I need to use a library (clj-webdriver) that relies on Clojure *1.3.0* What to do? -- You received this message because

Re: Errors w/ dynamic symbols in macro-utils or monads?

ah: http://dev.clojure.org/display/design/Where+Did+Clojure.Contrib+Go clojure.contrib.monads - Migrated to clojure.algo.monads - lead Konrad Hinsenhttp://dev.clojure.org/jira/secure/ViewProfile.jspa?name=khinsen . - Status: latest build

Re: Errors in Clojure

Hi, The last thrown Exception/Error is kept in the var *e. You should be able to view the complete stack trace of the last thrown exception by calling something like: (.printStackTrace *e) Ambrose 2011/8/19 J. Pablo Fernández pup...@pupeno.com Hello Clojurians, I'm struggling to work with

Re: Errors in Clojure

This is postgresql exception so problem is there (it's not Clojure's one). Just try to connect via some other tool to confirm this, use psql in command line, for example. Maybe there is missing group role that is linked to login role 'mgr'. PS: I hope that password is not a confidential one :)

Re: Errors in Clojure

Petr, I do not care about this particular error, but about how to deal with this one liners. Ambrose's reply is what I needed, and no, it's not PostgreSQL problem. It's a library trying to establish a connection when it shouldn't with credentials that should never be used because I never

Re: Errors in Clojure

2011/8/19 J. Pablo Fernández pup...@pupeno.com: Petr, I do not care about this particular error, but about how to deal with this one liners. Ambrose's reply is what I needed, and no, it's not PostgreSQL problem. It's a library trying to establish a connection when it shouldn't with credentials

Re: errors?

Don't be discouraged. At work I use Eclipse with all sorts of mature tools (this is Java). It is, more or less, pretty easy to use. At home I use Aquamacs with a simple clojure-mode.el. I can produce lines of code many times faster and easier with the later. No doubt a big part reflects the

Re: errors?

But how do you get rid of the (NO_SOURCE_FILE:0) messages for every single error? I'd really like to know the line number of the function that threw the error. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups

Re: errors?

Try frequently doing: (use :reload 'fully.qualified.name.of.my.file) When you are interactively adding code to the REPL (by typing or through Slime or whatever) it doesn't know the line number. If you reload the file containing the offending code, it will. I usually have a comment block like

Re: errors?

Try frequently doing: all of this sounds like it would be great if i understood enough of it all to make some patches to the source code -- it strikes me as rather newbie-unfriendly the way it currently all works. $0.02. sincerely. --~--~-~--~~~---~--~~ You

Re: errors?

On Mar 13, 11:50 pm, Raoul Duke rao...@gmail.com wrote: i'm up to date with the clojure jar. the error messages i get seem awfully terse and not particularly helpful in learning what i'm doing wrong. for example, with the code below, when i try (bs 0 (vector 1 2 3)) i get

Re: errors?

On Mar 13, 2009, at 7:50 PM, Raoul Duke wrote: i'm up to date with the clojure jar. the error messages i get seem awfully terse and not particularly helpful in learning what i'm doing wrong. for example, with the code below, when i try (bs 0 (vector 1 2 3)) i get java.lang.ClassCastException:

Re: errors?

thanks, all, for the notes! i will try those out. sincerely. --~--~-~--~~~---~--~~ 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