On 16 Mrz., 23:36, Raoul Duke <rao...@gmail.com> wrote: > please, for those who aren't Erlang nerds, also see Dialyzer. > > http://www.it.uu.se/research/group/hipe/dialyzer
Funny, I just wanted to post exactly that link. It is very impressive what that tool did: "Dialyzer has been applied to large code bases, for example the entire code base of AXD301 consisting of about 2,000,000 lines of Erlang code, and has identified a significant number of software defects that have gone unnoticed after years of extensive testing." In fact, it is this very tool, the Erlang Dialyzer that made me start thinking about this whole thing. The Dialyzer will infer the types from the sources, without hints of the developers. This means that it can not find all bugs. But it uses the information that exists even in a dynamically typed language to spit out warnings about type problems, but also about other discrepancies. If you follow the link, also read the pdfs they put online, such as: http://user.it.uu.se/~kostis/Papers/bugs05.pdf It's just five pages, and written not only for experts of static type systems. If the Dialyzer can do all this without having an optional type system in Erlang, then it should be obvious what would be possible, if Rich agrees and finds the time/resources to add one in Clojure. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
