I could only skim today's big discussion thread, so please ignore this
devil's advocate playing if it's unhelpful...
What about doing eating one's own dogfood, and doing experimental new
libraries in PLaneT instead?
If, on the other hand, it's for code-sharing of internal-use-only code
within PLT Scheme, why not just put it wherever other internal-use-only
code goes?
If it's for internal code-sharing *plus* external use with the warning
that it's unstable, why not keep it internal-use-only until it's ready,
rather than dilute the PLT Scheme brand?
--
http://www.neilvandyke.org/
_________________________________________________
For list-related administrative tasks:
http://list.cs.brown.edu/mailman/listinfo/plt-dev
