[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
- To: srfi-83@xxxxxxxxxxxxxxxxx
- Subject: languages
- From: Alex Shinn <alexshinn@xxxxxxxxx>
- Date: Fri, 13 Jan 2006 18:15:30 +0900
- Delivered-to: srfi-83@xxxxxxxxxxxxxxxxx
- Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; b=CzR0yucUuiRxAi16kI/stlhUZ6LgwJciZYpW/kXSZfdAbKu8eSYTY++HzryLHs9h3719TynvDGdLNDG0W2g6/m7WGup4KoBWXTsDMfiH4gnFbXrJ6s0aQv7IHiK9RwxMV9jjIan8Iwx29uzVIK7s6WOcKPCmDANh7vv+EDBEQqI=
First a minor nitpick, why does the library declaration reserve an
explicit required parameter for the language, when there is currently
no way to write your own or specify alternate languages? Even when
there is such a feature, in (imagine some fantastically huge percent)
of all cases people will use the default.
It seems to make much more sense to optimize for the common case and
use a separate, optional form to specify a language, such as Chez's
IMPORT-ONLY. If you don't like the name because it sounds too close
to the ONLY import form, you can change it to LANGUAGE or
PARENT-MODULE or whatever:
It's more descriptive too.
Also, I agree with the earlier post that strings are being abused
here for the names, and SEXPs would be the natural solution.
Speaking of which, something really needs to be said about the naming
convention. Once you get people sharing modules you need a naming
hierarchy, unless you want to descend into CPAN naming hell.
Extrapolating from the default language, it looks like we can expect: