On 2010 May 5, at 10:32 AM, Stuart Halloway wrote:
==== A SIMPLER SOLUTION: WARN, DON'T ERR ====
That's a lot better than being dead with an error.
Is there a way to turn those warnings back into errors for those
really paranoid of us?
==== PROMOTION AND DEPRECATION ====
With "warn on name collision" in place, the sane way to promote from
one library to another is to copy the vars into their new home, but
to also leave the old ones in place (for a while). The old vars can
be marked with {:deprecated "some.version.no"}, and old clients can
continue to use them.
Is there some way to control where the warnings "go"? If they happen
in a server whose stdout/stderr aren't being read by a human (or which
has been directed to /dev/null)...
I think it is a great idea in general. IIRC Common Lisp addressed this
with shadowing-import...
-D
--
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
