On Fri, Jul 20, 2012 at 8:40 PM, David A. Wheeler <dwhee...@dwheeler.com> wrote: > Alan Manuel Gloria: >> I think I want to reorganize them module's interfaces. >> >> And I think I want to put them in a readable-discuss subdirectory so >> that module names are something like (readable-discuss sugar) or some >> such. That will help making them easier to fob around in various >> Scheme's package systems I think; certainly Guile would appreciate it that >> way. > > Moving them to a subdirectory is fine. > > We need to have *REALLY GOOD NAMES* for the public interface. Good names > make all the difference for ease-of-use. For example, don't use the name > "readable-discuss" - that's the mailing list name, not the group name, and > it's long anyway. But "readable" as a module name might work. Anyone have a > better idea?
Wait wait wait. Isn't the typical protocol to put the provenance of a module somewhere in it's hierarchical name? Since sweet-expr are a project of the readable-discuss mailinglist, I thought it best to put the name readable-discuss on it. Basically, the module name means "This is readable-discuss's project, the sweet-reader". What should the protocol be for the module name? Sincerely, AmkG ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ Readable-discuss mailing list Readable-discuss@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/readable-discuss
