Re: Couldn't find how to build an executable out of Lisp code

Pierre THIERRY wrote:
BTW, I end up with a 28Mb core file with :executable t and 27Mb when
nil. Why is it so heavy?

In Lisp, NIL is so overloaded with many important meanings, that it
takes nearly a full megabyte to implement them all.

:)

.

Relevant Pages

  • Re: Implementing custom containers in Lisp
    ... CMU Common Lisp 18b, running on shell.xxx.com ... distinguish between immediate values and handles to heap objects, ... *all* integers are in fact BIGNUMs or equivalent, immutable objects on ... NIL ...
    (comp.lang.lisp)
  • Re: Predicate for lexical bindings
    ... I assume you mean that you have started up an interactive Lisp ... lower level of parse, sees the word "let" which sees there already ... but there's no symbol by that name (in the current package) so ... so it puts NIL into the CDR of that same CONS cell to ...
    (comp.lang.lisp)
  • Re: Advice for a new lisper
    ... This is my first experience with lisp, ... (defun simplify-card (card) ... unless return nil) ...
    (comp.lang.lisp)
  • Re: can someone explain this quote by Tim Daly?
    ... What's so special about nil and in the context of being a Lisp? ... Language design based on ... nothing contrived about saying that language designers do, in fact, ...
    (comp.lang.lisp)
  • Re: Why forth is not popular
    ... >> it would be very surprising if a production-quality Lisp system ... > (cdr nil), for example. ... SEGV trap handler can be an issue again. ... Douglas Johnson, Trap Architectures for Lisp Systems, pages 79-86, ...
    (comp.lang.forth)