Roberto Ierusalimschy
|
178246062c
reuse `sweeplist' for all lists
|
21 years ago |
Roberto Ierusalimschy
|
a4e1230f95
better way to control open upvalues
|
21 years ago |
Roberto Ierusalimschy
|
b876ec61c0
new (temporary?) API for garbage collector
|
21 years ago |
Roberto Ierusalimschy
|
2aaf7394ad
more and better tools (assertions & inspectors) to check incremental GC
|
21 years ago |
Roberto Ierusalimschy
|
beb2aa5a46
atomic operations are not GC "states"
|
22 years ago |
Roberto Ierusalimschy
|
47fc57a252
`TObject' renamed to `TValue' + other name changes and better assertions
|
22 years ago |
Roberto Ierusalimschy
|
df429f163a
First version of incremental GC
|
22 years ago |
Roberto Ierusalimschy
|
fe595a45c2
`grayagain' list
|
22 years ago |
Roberto Ierusalimschy
|
9db1942bac
sweep of strings also incremental
|
22 years ago |
Roberto Ierusalimschy
|
c6eac44a94
two different white flags (to distinguish dead elements from new ones)
|
22 years ago |
Roberto Ierusalimschy
|
8878554b85
single list for all collectible objects, with udata separated at the
|
22 years ago |
Roberto Ierusalimschy
|
af850484a9
default metatable can be NULL
|
22 years ago |
Roberto Ierusalimschy
|
1d10acb355
incremental GC phases
|
22 years ago |
Roberto Ierusalimschy
|
57b6ed6815
initial implementation of white/gray/black coloring
|
22 years ago |
Roberto Ierusalimschy
|
366e4af3c9
towards incremental GC
|
22 years ago |
Roberto Ierusalimschy
|
ab7d9bfd0c
cleaner code for manipulation of `marked' field
|
22 years ago |
Roberto Ierusalimschy
|
8332d5c8a5
parser fully reentrant(!)
|
22 years ago |
Roberto Ierusalimschy
|
a0a384a6b1
bug: userdata to be collected still counts into new GC threshold,
|
22 years ago |
Roberto Ierusalimschy
|
fa26d294ae
new way to control `pc' of running functions
|
22 years ago |
Roberto Ierusalimschy
|
9e05503ffa
bug: C functions also may have stacks larger than current top
|
22 years ago |
Roberto Ierusalimschy
|
ecf5730c0c
(much) smarter way to clear weak tables
|
22 years ago |
Roberto Ierusalimschy
|
572a69df78
Lua does not need all those different types...
|
22 years ago |
Roberto Ierusalimschy
|
0d88545b82
warnings from several compilers (mainly typecasts when lua_Number is float)
|
22 years ago |
Roberto Ierusalimschy
|
ab9e062928
name changes to avoid name collision between macros and variables
|
22 years ago |
Roberto Ierusalimschy
|
7a40cdbda0
different variables for number of upvalues and size of upvalue array
|
22 years ago |
Roberto Ierusalimschy
|
6f207b15fb
resist errors in finalizers during lua_close
|
22 years ago |
Roberto Ierusalimschy
|
dd8edecae1
new functions to manipulate upvales (get/setupvalue)
|
23 years ago |
Roberto Ierusalimschy
|
27c6b4d422
each .c file defines its own name
|
23 years ago |
Roberto Ierusalimschy
|
c75c3cfd19
avoid names `str...' (may conflict with string.h)
|
23 years ago |
Roberto Ierusalimschy
|
e47baca75a
warnings from Visual C++
|
23 years ago |