[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: compiled vs. uncompiled code
- To: email@example.com
- Subject: Re: compiled vs. uncompiled code
- From: haible (Bruno Haible)
- Date: Thu, 4 Aug 94 16:56:23 +0200
> Can someone please explain why my program bombs when I load in raw
> source code but not when I load in compiled code.
Behaviour differences between interpreted and compiled code can have the
- Use of EVAL-WHEN (COMPILE).
- Macros which destructively modify the code being interpreted or compiled.
Evil. You can detect this using CLISP binaries which have IMMUTABLE
support built in.
> *** - Lisp stack overflow. RESET
Compiled code uses less stack space. Maybe your code is deeply recursive.
Find out like this: interrupt just before you get the stack overflow
message, and look at the stack using the Backtrace commands.