| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| ... | |
| |
|
|
|
|
|
|
| |
a = array.new(1000)
for i=1,1000 do
a:set(i, 1/i)
end
print(a:get(10)) -- 0.1
|
| | |
|
| |
|
|
| |
And it seems simpler to me.
|
| |
|
|
|
|
|
|
|
| |
User-defined C data.
I think I have some understanding of the Lua stack now. It's a different
kind of verbose, error-prone syntax than Mu that requires me to play
computer in my head. But I don't fully grok metatables yet. At least not
well enough to grok everything that's going on in lcurses/ext.
|
| | |
|
| |
|
|
|
|
|
|
| |
Putting together two resources:
https://lucasklassmann.com/blog/2019-02-02-how-to-embeddeding-lua-in-c/#exposing-a-simple-variable
https://www.lua.org/manual/5.3/manual.html, section 2.1, "Values and Types", particularly the description of light user data.
And lo, I see lua_pushlightuserdata in lapi.c
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
| |
Lua's power may come from extensibility, but the indirections are
currently in the way
|
| |
|
|
|
|
| |
lua_State contains these StkId fields (stack, stack_last, base, top)
that expand to a pointer of a struct containing a Lua value and an int.
Unclear how it's used, or how you build a stack out of it.
|
| |
|
|
|
|
|
|
|
|
| |
At this point I'm done making this repo ncurses-ready. Remaining files
that allude to stdin/stdout/stderr:
lauxlib.c - unclear how these primitives should work; may kill them
ldblib.c - unclear what debug experience should be
liolib.c - might kill or simulate these
luac.c - let the compiler continue to be a terminal program
|
| |
|
|
| |
luaconf.h now no longer refers to stdin/stdout/stderr.
|
| |
|
|
| |
lua.c now no longer refers to stdin/stdout/stderr.
|
| |
|
|
|
|
|
|
|
|
|
|
| |
Currently working:
> print(1)
1
> print(2)
2
Print's newline doesn't return to column 0 yet.
Ctrl-d no longer works. Ctrl-c exits cleanly.
|
| | |
|
| | |
|
| |
|
|
| |
We're going to be using full-on ncurses.
|
| | |
|
|
|
https://www.lua.org
|