Re: case sensitivity of provide, require and module-provide-asdf
Raymond Toy <[email protected]>
| Newsgroups | gmane.lisp.clisp.devel |
|---|---|
| Message-ID | <[email protected]> |
>>>>> "Pascal" == Pascal J Bourguignon <[email protected]> writes: Pascal> Now, all those variables can (and most of them probably should) be set Pascal> in the rc file (~/.clisprc.lisp, etc) by the user. Pascal> The consequences are that: Pascal> 1- as a user, you must know what you've put in the rc file, and Pascal> therefore what is the current setting of those variables. You could Pascal> have: Pascal> (SETF (READTABLE-CASE *READTABLE*) :PRESERVE) Pascal> in your rc file, and use uppercase letters (their real case) for all Pascal> the CL symbols. Pascal> 2- I would argue that library sources should NOT assume a readtable, and Pascal> like they include a IN-PACKAGE form at the start of each source file, Pascal> they should also include a form setting the *readtable*, such as: Pascal> (EVAL-WHEN (:COMPILE-TOPLEVEL :LOAD-TOPLEVEL :EXECUTE) Pascal> (SETF *READTABLE* (COPY-READTABLE NIL))) Pascal> in each source file, or at the very least, there should be a way in Pascal> ASDF (and other similar system definition systems), to specify the Pascal> readtable to be used to load and read the sources of the library. If a user wants to make his life difficult in using other peoples' code, go for it. Maybe hack your own load and compile-file function to change the read table case. Sane people just use the default and enjoy being able to use other people's code without problems. -- Ray ------------------------------------------------------------------------------ What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic patterns at an interface-level. Reveals which users, apps, and protocols are consuming the most bandwidth. Provides multi-vendor support for NetFlow, J-Flow, sFlow and other flows. Make informed decisions using capacity planning reports. https://ad.doubleclick.net/ddm/clk/305295220;132659582;e _______________________________________________ clisp-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/clisp-devel