mirror of
https://gitlab.com/embeddable-common-lisp/ecl.git
synced 2026-03-15 17:30:37 -07:00
67 lines
1.6 KiB
Text
67 lines
1.6 KiB
Text
THINGS IN THIS FILE
|
|
===================
|
|
|
|
This file documents assumptions which are made throughout the ECLS code. Most
|
|
of them are critical and a lot of code relies on them, some others are very
|
|
localized but in critical points (eval, apply, etc). In general great care
|
|
must be taken so that changes in ECLS do not break these "invariants".
|
|
|
|
|
|
REAL BUGS
|
|
=========
|
|
|
|
* Routines in bind.c do not check length of arguments and may cause buffer
|
|
overflows.
|
|
|
|
GCC SPECIFICS
|
|
=============
|
|
|
|
* Functions with a variable number of arguments are called with the
|
|
same protocol as ordinary functions, i.e., the following code is
|
|
valid
|
|
|
|
#in "foo.c"
|
|
extern int fa(int foo, ...);
|
|
int test(object x) {
|
|
faa(1, x);
|
|
}
|
|
|
|
#in "faa.c"
|
|
int faa(int foo, object x) {
|
|
...
|
|
}
|
|
|
|
|
|
OPERATING SYSTEM
|
|
================
|
|
|
|
* Stack checks are required in compiled code to make sure recursion
|
|
does not get too deep. This makes sense in multithreaded code, but
|
|
do unix-like operating systems really provide no stack protection?
|
|
|
|
|
|
ECLS CODE INVARIANTS
|
|
====================
|
|
|
|
* C structs are aligned at least at 4 bytes, so that Cnil is a valid
|
|
object pointer.
|
|
|
|
* "struct ecl_symbol" and "struct ecl_cons" share fields so that
|
|
Cnil->c.c_car == Cnil->c.c_cdr == Cnil.
|
|
|
|
* "struct ecl_array", "struct ecl_vector", "struct ecl_string, "struct
|
|
ecl_bitvector" share a number of fields, such as "*_dim", "*_self", etc.
|
|
|
|
* Boehm's garbage collector returns pointers with two lower bits set
|
|
to zero, i.e.,
|
|
|
|
((int)GC_malloc(n)) & 3 == 0
|
|
|
|
* Frame/binding/history stacks cannot be resized.
|
|
|
|
* DATA_START % LISP_PAGESIZE == 0
|
|
|
|
;;; Local Variables: ***
|
|
;;; mode:text ***
|
|
;;; fill-column:79 ***
|
|
;;; End: ***
|