Re: upcoming revision, need feedback
R. Kent Dybvig
(11 Jan 2010 20:52 UTC)
|
Re: upcoming revision, need feedback
Derick Eddington
(12 Jan 2010 02:11 UTC)
|
Re: upcoming revision, need feedback
R. Kent Dybvig
(12 Jan 2010 03:52 UTC)
|
Re: upcoming revision, need feedback
Thomas Bushnell BSG
(12 Jan 2010 04:24 UTC)
|
Re: upcoming revision, need feedback
Derick Eddington
(12 Jan 2010 06:18 UTC)
|
Re: upcoming revision, need feedback
Thomas Bushnell BSG
(12 Jan 2010 06:27 UTC)
|
Re: upcoming revision, need feedback
Derick Eddington
(12 Jan 2010 07:05 UTC)
|
Re: upcoming revision, need feedback Thomas Bushnell BSG (12 Jan 2010 07:16 UTC)
|
Re: upcoming revision, need feedback
Derick Eddington
(12 Jan 2010 09:00 UTC)
|
Re: upcoming revision, need feedback
R. Kent Dybvig
(27 Jan 2010 20:58 UTC)
|
Re: upcoming revision, need feedback
Derick Eddington
(28 Jan 2010 00:45 UTC)
|
Re: upcoming revision, need feedback
Vitaly Magerya
(28 Jan 2010 10:39 UTC)
|
Re: upcoming revision, need feedback
Derick Eddington
(28 Jan 2010 17:45 UTC)
|
On Mon, 2010-01-11 at 23:05 -0800, Derick Eddington wrote: > On Mon, 2010-01-11 at 22:27 -0800, Thomas Bushnell BSG wrote: > > Well, part of this is about the value of the srfi in general. I think > > it would be better if it said, explicitly, this is a suggested binding > > for r6rs libraries on Unix systems, and other systems with similar > > directory structures. > > Okay, I'll change the first sentence of the Abstract section to be: > > This SRFI defines a standard for naming and finding files > containing libraries, for Unix-like and Windows platforms, where > a library name is a list of symbols. > > I think the rest of your message is failing to understand the purpose of > this SRFI. > Why do you suppose C has never specified any mapping between #include <> directives and directory layouts? Not even Posix has one. This has not hampered C's usability or portability. Thomas