mirror of
https://github.com/elua/elua.git
synced 2025-01-08 20:56:17 +08:00
Fix typos in documentation
This commit is contained in:
parent
eed1f7492d
commit
b49a11f4a2
@ -3,9 +3,9 @@ $$HEADER$$
|
||||
<p>The EGC (Emergency Garbage Collector) patch was originally written for Lua by Robert Jakabosky, who was kind enough to port it to <b>eLua</b>. You can find the author's detailed
|
||||
description of the patch <a href="http://lua-users.org/wiki/EmergencyGarbageCollector">here</a>. In short, what it does is that it lets you run a garbage collection cycle in Lua in a low memory
|
||||
situation, from inside Lua's memory allocation function (something that the current version of Lua can't do out of the box). By forcing a garbage collection cycle, Lua can reclaim memory that's
|
||||
not in use anymore, thus making more memory available for your program. The downside is reduced execution speed, as a direct result of running the gargabe collector when needed. For some
|
||||
not in use any more, thus making more memory available for your program. The downside is reduced execution speed, as a direct result of running the garbage collector when needed. For some
|
||||
applications, reducing the execution speed to fit the application in memory might be acceptable, and for other applications it might not. As usual, it all depends on your application. As a generic
|
||||
guideline, if your application isn't concerned with realtime processing, you should be fine with sacrifing execution speed to get more memory in many real life scenarios.</p>
|
||||
guideline, if your application isn't concerned with realtime processing, you should be fine with sacrificing execution speed to get more memory in many real life scenarios.</p>
|
||||
<p>In <b>eLua</b>, the EGC patch can be configured to run in 4 different modes:</p>
|
||||
<ol>
|
||||
<li><b>disabled</b>: EGC inactive, no collection cycle will be forced in low memory situations.</li>
|
||||
|
Loading…
x
Reference in New Issue
Block a user