Alan Manuel Gloria: > Wait wait wait. Isn't the typical protocol to put the provenance of a > module somewhere in it's hierarchical name?
Sure! > 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". Ah, I see where we differ. I use "readable" as the short name of the overall project, not "readable-discuss". I use "readable-discuss" as the name of our current mailing list, so that we could have OTHER mailing lists if we needed to. In any case, we also have a wiki, git repo, and so on. Since this is the result of the entire project, not just the current mailing list, the module name should reflect the name of the whole project too. After all, the front page is http://readable.sourceforge.net/ (not http://readable-discuss.sourceforge.net/), and so on. The full project name is currently "Readable Lisp S-expressions" see (http://sourceforge.net/projects/readable/) but that's way too long. --- David A. Wheeler ------------------------------------------------------------------------------ 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
