On Apr 1, 3:23 pm, Vincent Foley wrote:
> I have no experience with gradual typing, but I'd love to try it. It
> seems there are many situations where dynamic typing just makes things
> easier than in a language like Haskell, however I long for their
> ability to verify correctness at compile
I have no experience with gradual typing, but I'd love to try it. It
seems there are many situations where dynamic typing just makes things
easier than in a language like Haskell, however I long for their
ability to verify correctness at compile time.
Vince
On Mar 29, 10:49 am, André Thieme wr
On Wed, Apr 1, 2009 at 9:10 AM, hughw wrote:
> I don't mind scrolling through the long stack crawl to discover where
> my error is. but I do wish the initial error report could somehow give
> me the information, rather thanrequiring the two step process (and
> switching windows when using the sli
On Apr 1, 10:53 am, hughw wrote:
> I retract my comment! Although I agree with the sentiment that
> improvederrorreportingwould be great, I'm unsure exactly what I
> want.
>
Clarification:
In the SLIME repl I invoke my function. It reports the error as
java.lang.ClassCastException: java.lang
On Apr 1, 10:43 am, hughw wrote:
> On Mar 28, 8:24 pm, Stuart Sierra wrote:
> [snip]
>
>
>
> > Also, if you're using SLIME, you lose line numbers every time you
> > evaluate a form in the buffer. Type
> > (require your.namespace :reload) at the REPL to get them back.
>
> This advice did not w
On Mar 28, 8:24 pm, Stuart Sierra wrote:
[snip]
>
> Also, if you're using SLIME, you lose line numbers every time you
> evaluate a form in the buffer. Type
> (require your.namespace :reload) at the REPL to get them back.
>
This advice did not work for a situation I am encountering now and
enc
Mark Volkmann writes:
Hi Mark,
>> The long list of stuff you get is called a Stack Trace. It will save
>> your life someday.
>
> Definitely having the ability to see the full stack trace is be
> useful. I wonder though if that should be the default output. Maybe by
> default only lines from the
On 29 Mrz., 01:55, Glen Stampoultzis wrote:
> Hi, I've been really enjoying getting to know clojure. It's an awesome
> language that has got me very interested in learning more. One thing that
> hasn't left me impressed is the error reporting.
> [...]
> There are a few things wrong here and with
On Sun, Mar 29, 2009 at 4:26 AM, Rayne wrote:
>
> The long list of stuff you get is called a Stack Trace. It will save
> your life someday.
Definitely having the ability to see the full stack trace is be
useful. I wonder though if that should be the default output. Maybe by
default only lines fr
The long list of stuff you get is called a Stack Trace. It will save
your life someday.
--~--~-~--~~~---~--~~
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
2009/3/29 Stephen C. Gilardi
>
> On Mar 28, 2009, at 10:31 PM, Glen Stampoultzis wrote:
>
> It wasn't really this specific problem that I wanted to point out but more
>> to trigger a rethink of how errors are reported back to the user.
>>
>
> I understand, but without specifying which Clojure yo
On Mar 28, 2009, at 10:31 PM, Glen Stampoultzis wrote:
It wasn't really this specific problem that I wanted to point out
but more to trigger a rethink of how errors are reported back to the
user.
I understand, but without specifying which Clojure you're using and
giving an example of how
It wasn't really this specific problem that I wanted to point out but more
to trigger a rethink of how errors are reported back to the user.
Here's an example that gives an error somewhat similar to the one I posted:
(defn testing [a b] (print a b))
(testing)
java.lang.NoSuchMethodError:
java.lan
On Mar 28, 7:55 pm, Glen Stampoultzis wrote:
> I recently got this one that left me scratching my head:
>
> java.lang.NullPointerException (splat.clj:0)
> at clojure.lang.Compiler.eval(Compiler.java:4533)
In my experience, an error at line 0 means something wrong with the
(ns...) call at
On Mar 28, 2009, at 8:01 PM, Glen Stampoultzis wrote:
Sorry I just realized I was a bit ambiguous with this. The
exception does show the line number (in the second stack trace).
But it's gone missing in the top one.
Is this with the current svn or most recent release of Clojure? It
wou
Sorry I just realized I was a bit ambiguous with this. The exception does
show the line number (in the second stack trace). But it's gone missing in
the top one.
2009/3/29 Glen Stampoultzis
> Hi, I've been really enjoying getting to know clojure. It's an awesome
> language that has got me ver
Hi, I've been really enjoying getting to know clojure. It's an awesome
language that has got me very interested in learning more. One thing that
hasn't left me impressed is the error reporting.
I recently got this one that left me scratching my head:
java.lang.NullPointerException (splat.clj:0)
17 matches
Mail list logo
