unbroken naming conventions
William D Clinger
(22 Jul 2008 04:28 UTC)
|
Re: unbroken naming conventions
David Van Horn
(22 Jul 2008 14:20 UTC)
|
Re: unbroken naming conventions
Matthew Flatt
(22 Jul 2008 14:36 UTC)
|
Re: unbroken naming conventions
Grant Rettke
(22 Jul 2008 15:37 UTC)
|
Re: unbroken naming conventions
David Van Horn
(22 Jul 2008 15:59 UTC)
|
Re: unbroken naming conventions
Matthew Flatt
(22 Jul 2008 16:39 UTC)
|
Re: unbroken naming conventions Abdulaziz Ghuloum (22 Jul 2008 17:39 UTC)
|
Re: unbroken naming conventions Abdulaziz Ghuloum 22 Jul 2008 17:17 UTC
On Jul 22, 2008, at 8:59 AM, David Van Horn wrote: > Is it important to the implementors that the naming convention > avoid such characters? No. Implementations are supposed to handle all valid library names (i.e., anything that's a list of symbols, whatever their content might be). It might be confusing for the users though as there is no "standard" library-name->file- name mapping. (ikarus uses "srfi/%3a1.sls" for srfi 1 while mzscheme uses srfi/% 3A1.sls, note the case difference which might just be an artifact of the case of the string returned by (number->string (char->integer #\:) 16) under the two implementations)