--
You received this message because you are subscribed to the Google Groups "Clojure Dev" group.
To post to this group, send email to cloju...@googlegroups.com.
To unsubscribe from this group, send email to clojure-dev...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/clojure-dev?hl=en.
Please start a page at dev.confluence.org to capture the decisions being proposed/made. My suspicion is that we can all agree on the following:
* converting to data
* canonicalizing names
And will continue to argue about
* specific formatting.
Whatever we come up should capture the "everything prior to formatting" part in a function. That way individual tools (or users) can configure the last bit as they see fit.
Another tagentially-related thing to consider: a generic exception type in Clojure, bearing a map of information. This would get rid of many superfluous project-specific gen-classes, plus the compilation and binary dependencies that ensue.
Stu
Agreed! I'm a huge fan of the alignment, not to mention the colorized
stack traces. Customizable filtering is also pretty important.
Thanks for moving the discussion forward. =)
-Phil
Actually clojure.contrib.condition does this. It's not well-known; I
think people could benefit from wider knowledge of it. I think it's a
good candidate for eventual promotion, but it probably needs to see
wider usage first. It's quite useful.
-Phil
The data structure idea is fine, all strings maybe not.
Also, needs a good strategy for distinguishing the kinds of entries
(e.g. fns vs methods)
As Stu said, a Confluence page would be the next step.
Rich
To unsubscribe from this group, send email to clojure-dev...@googlegroups.com.
- Mark
> -Phil