Re: ANSI CL support
"Pascal J. Bourguignon" <[email protected]>
| Newsgroups | gmane.lisp.clisp.devel |
|---|---|
| Message-ID | <[email protected]> |
Raymond Toy <[email protected]> writes: > A friend pointed this out to me: > > (apropos "-ANSI") -> > *COERCE-FIXNUM-CHAR-ANSI* variable > *FLOATING-POINT-CONTAGION-ANSI* variable > *FLOATING-POINT-RATIONAL-CONTAGION-ANSI* variable > *LOOP-ANSI* variable > *MERGE-PATHNAMES-ANSI* variable > *PARSE-NAMESTRING-ANSI* variable > *PHASE-ANSI* variable > *PRINT-EMPTY-ARRAYS-ANSI* variable > *PRINT-PATHNAMES-ANSI* variable > *PRINT-SPACE-CHAR-ANSI* variable > *PRINT-UNREADABLE-ANSI* variable > *SEQUENCE-COUNT-ANSI* variable > > The ANSI CL spec is now almost 20 years old and hasn't changed since > then. I didn't check to see what all of variables actually do, but > isn't it time to make these default to T? Or at least some of them? Always run clisp with -ansi (for the case you also give -norc), and put (setf custom:*ansi* t) in ~/.clisprc.lisp -- __Pascal Bourguignon__ http://www.informatimago.com/ ------------------------------------------------------------------------------ Shape the Mobile Experience: Free Subscription Software experts and developers: Be at the forefront of tech innovation. Intel(R) Software Adrenaline delivers strategic insight and game-changing conversations that shape the rapidly evolving mobile landscape. Sign up now. http://pubads.g.doubleclick.net/gampad/clk?id=63431311&iu=/4140/ostg.clktrk _______________________________________________ clisp-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/clisp-devel