[Scheme-reports] Module Versioning Roderic Morris (14 Jan 2012 17:18 UTC)
Re: [Scheme-reports] Module Versioning Grant Rettke (14 Jan 2012 20:56 UTC)
Re: [Scheme-reports] Module Versioning John Cowan (14 Jan 2012 22:50 UTC)

Re: [Scheme-reports] Module Versioning Grant Rettke 14 Jan 2012 20:56 UTC

I think that what was once named Snow will be handing that duty?

http://lists.scheme-reports.org/pipermail/scheme-reports/2011-September/001494.html

On Sat, Jan 14, 2012 at 11:08 AM, Roderic Morris <roderyc@gmail.com> wrote:
> Has there been much discussion about this? I haven't found any on this
> list (mostly because the only interface to the archive I found is
> impossible to search), or much on the wiki. It seems absolutely
> essential to any language where code is shared at large. If they've
> been purposefully omitted, what sort of strategy would you expect
> library writers / users to use instead? What should happen when a
> program depends on libraries A and B, which both depend on library C,
> but at different points in time, between which C has had substantial
> changes in its interface?
>
> -Roderic
>
> _______________________________________________
> Scheme-reports mailing list
> Scheme-reports@scheme-reports.org
> http://lists.scheme-reports.org/cgi-bin/mailman/listinfo/scheme-reports

--
http://www.wisdomandwonder.com/
ACM, AMA, COG, IEEE

_______________________________________________
Scheme-reports mailing list
Scheme-reports@scheme-reports.org
http://lists.scheme-reports.org/cgi-bin/mailman/listinfo/scheme-reports