On Jan 24, 2013, at 11:27, Michael Klishin wrote: > So, if you have something specific to say on the topic, say it here.
Well, these comments more general in nature; hope that's OK... I find Clojure's default error messages to be noisy, ugly, and hard to decipher. What I'd like is a short, clear explanation of the problem and a way to get the details, if desired. Ben Schneiderman gives a lot of good advice on error messages in "Designing the User Interface" http://www.amazon.com/dp/0201694972 The second edition of the book includes this table (8.1): Error-Message Guidelines * Be as specific and precise as possible. * Be constructive: indicate what needs to be done. * Use a positive tone: avoid condemnation. * Choose user-centered phrasing. * Consider multiple levels of messages. * Keep consistent grammatical form, terminology, and abbreviations. * Keep consistent visual form and placement. The book (economically available from Amazon) covers each point in detail. This might provide useful criteria for any rework. -r -- http://www.cfcl.com/rdm Rich Morin http://www.cfcl.com/rdm/resume r...@cfcl.com http://www.cfcl.com/rdm/weblog +1 650-873-7841 Software system design, development, and documentation -- -- 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
