Tags give the ability to mark specific points in history as being important
-
xb-lua54-r84
ca86dcaf · · -
xb-lua54-r83
e6258991 · ·Lend-out + run lua_state - fc confirmed Confirmed (i.e. validated) against project mycalc that can now use lua_State when not busy for internal service-commands. Additional: * Sessions race controlled using semaphore * Init/VM-create phase of single-sessions against dev/null * No more sleeps => Improved stability (xb-console)
-
xb-lua54-r82
c0738345 · ·New service API permitting lua_State to be shared * New service API permitting lua_State to be shared * Multisession fixes (regression)
-
xb-lua54-r81
85afcf43 · · -
xb-lua54-r80
07b9b33e · · -
xb-lua54-r2
52fb11b3 · ·Thread-saf(er) + history in sync Thread safety: ============== * Improved thread safety, particularly single-threaded VM's but even between a main process that is also a lua-VM (xb-console test app) * Affected domains: * GNU readline * LBM History in sync: ================ When xb-lua single-session is being used by an application that also uses GNU-readline, they will cross-contaminate each others history upon attach/detach. Keeping xb-lua's history it's own is achieved by history re-init/sync (i.e. write/read to/from file) though all it's life-stages. Applications needs to do the same, but mechanisms differ as they gave to do it in event-handlers (see mycalc)
-
xb-lua54-r1
adab3dac · · -
xb-lua54-r0
c9c632e6 · · -
xb-lua-r16
1a9ea9d1 · · -
xb-lua-r15
9193e2de · · -
xb-lua-r14
d1c336f5 · · -
xb-lua-r13
89c9e98c · · -
xb-lua-r12
11700f6a · · -
xb-lua-r11
b408292e · · -
xb-lua-r10
041cdaa6 · · -
-
-
-
-