On Apr 1, 3:23 pm, Vincent Foley <vfo...@gmail.com> 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 time.
>
> Vince
>
> On Mar 29, 10:49 am, André Thieme <splendidl...@googlemail.com> wrote:
>
> > On 29 Mrz., 01:55, Glen Stampoultzis <gst...@gmail.com> 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 clojure error reporting in
> > > general:
>
> > > 1. I'm not getting a line number for some reason.
> > > 2. I don't get any indication what the nature of the error is.
> > > 3. I get a big (nested) stack trace that has more to do with clojure
> > > compiler internals than my program.
>
> > I would like to make a comment that does not directly talk
> > about your specific issue, but about error reporting in
> > general.
> > I would love to hear more opinions about Gradual Typing for
> > Clojure. That would allow the compiler to catch errors before
> > the program is actually run. Your example that you gave at some
> > other point in this thread could have been caught during
> > compilation.
> > Please have a look at this
> > thread:http://groups.google.com/group/clojure/browse_thread/thread/7a48f48e4...
I have seen that NullPointer before, especially when you use a proxy
and don't have the import of the class defined. But on error
reporting. Clojure is the best 'new' language I have seen that has
good error reporting. It has really increased my productivity. For
example, if there is an error at a line of clojure code, I can go to
it (OK except for that particular one), that seems like a bug. But
the majority of the time when I have a code error on my end, I kind of
easily navigate to it.
Can you say that in the common lisp world? I laugh at the premise.
Good job on the error reporting in my opinion.
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---