[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: r6rs libraries, round two
From: |
Ludovic Courtès |
Subject: |
Re: r6rs libraries, round two |
Date: |
Mon, 29 Jun 2009 20:26:18 +0200 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/23.1.50 (gnu/linux) |
Hello!
Julian Graham <address@hidden> writes:
> It's a fine way of handling version-less dependencies, but I don't see
> how it solves the determinism issue. Let's say my program (or code
> stream or script or whatever you want to call it) uses libraries from
> two different authors. Author A trusts his dependencies to remain
> stable and doesn't use version specifiers in his library references;
> author B does use them.
IMO this example is not realistic. Libraries with a well defined API
stability policy provide ad hoc versioning mechanisms at the source
level, e.g., "(use-modules (gnome-2))". Likewise, applications
distributed as a source package and that aim to build on a wide range of
platforms are likely to explicitly check for the version of their
dependencies.
By saying Guile should "comply to the letter of the standard", I think
Andy meant to say it should do the minimum required to be
"standard-compliant".
Thanks,
Ludo'.
- Re: r6rs libraries, round two, Andy Wingo, 2009/06/01
- Re: r6rs libraries, round two, Ludovic Courtès, 2009/06/01
- Re: r6rs libraries, round two, Neil Jerram, 2009/06/03
- Re: r6rs libraries, round two, Julian Graham, 2009/06/27
- Re: r6rs libraries, round two, Andy Wingo, 2009/06/28
- Re: r6rs libraries, round two, Julian Graham, 2009/06/29
- Re: r6rs libraries, round two,
Ludovic Courtès <=