Every code is prone to produce runtime exceptions on some input (mainly StackOverflow or OutOfMemory). That's just one more reason to produce.
I agree that it is one harder to grasp for a non computer scientist, but it is quite a simple one to manage for the more advanced user. There is a difficult question beginner vs more knowledgeable people. I don't believe overflow exception is hard for a beginner. (They know how an integer is stored in a computer), but they should not need to write any annotations. On Sun, Jun 20, 2010 at 7:25 PM, Garth Sheldon-Coulson <g...@mit.edu> wrote: > Yes, you're right. I wasn't suggesting that someone without an > understanding of static types in general or Java types in particular would > be liable to write *unsafe* code. I was saying that he or she might be prone > to writing code that produces runtime exceptions, and that these exceptions > might not appear right away but rather only with certain runtime inputs. To > me, correct code is code that isn't liable to produce unexpected exceptions. > -- 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 Note that posts from new members are moderated - please be patient with your first post. 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
