29 entries in 0.375s
snsabot: Logged on 2019-08-30 04:12:47 spyked:
http://logs.nosuchlabs.com/log/trilema/2019-08-29#1931955 <-- recall, /me already wrote a
toy prototype as his introduction to ada. other than the fact that it looks noobish and requires work to integrate with the c-isms, writing logger on top of it would also require something along the lines of a. mod_adalisp and b. handling other wwwistic s
snsabot: Logged on 2019-08-29 18:21:10 asciilifeform: diana_coman: rly it oughta be in tmsr-
adalisp (tm)(r) but this apparently dun exist yet.
a111: Logged on 2019-02-04 16:59 mircea_popescu: im sure eg spyked would love ot give it a gander -- maybe he thereby learns asm and becomes as smart as ave1 for one, and maybe it helps his
adalisp for the other.
mircea_popescu: im sure eg spyked would love ot give it a gander -- maybe he thereby learns asm and becomes as smart as ave1 for one, and maybe it helps his
adalisp for the other.
☟︎ bvt: 2. i seem to remember but can't find right now a discussion (around time spyked published
adalisp) that making such a genesis should be ok. perhaps i am confused about the context of that discussion and did something stupid.
mircea_popescu: spyked evidently, if
adalisp isn't tabletop systems engineering, then what is it.
mircea_popescu: anyway, an
adalisp-os could in principle stand down on x86 arch eventually.
mircea_popescu: ada already has very strong bounds ~checks~. but if he's doing a whole
adalisp, well...
a111: Logged on 2017-11-20 12:19 spyked:
http://btcbase.org/log/2017-11-14#1737923 <-- also, spyked's
adalisp is missing more fundamental things, such as closures. it's an early prototype, barely usable, but > 0. interning is of course considered, but not added yet. anyway, phf, consider the following point: built-in symbols (car, cons, etc.) still have to point *somewhere*, and that somewhere must not be addressed in a C-machine style! symbols should point to Lisp memory (via
a111: Logged on 2017-11-20 12:19 spyked:
http://btcbase.org/log/2017-11-14#1737923 <-- also, spyked's
adalisp is missing more fundamental things, such as closures. it's an early prototype, barely usable, but > 0. interning is of course considered, but not added yet. anyway, phf, consider the following point: built-in symbols (car, cons, etc.) still have to point *somewhere*, and that somewhere must not be addressed in a C-machine style! symbols should point to Lisp memory (via
spyked: I'll get back to the "working cli/tui js browser" problem later, back to
adalisp for now.
spyked:
http://btcbase.org/log/2017-11-14#1737923 <-- also, spyked's
adalisp is missing more fundamental things, such as closures. it's an early prototype, barely usable, but > 0. interning is of course considered, but not added yet. anyway, phf, consider the following point: built-in symbols (car, cons, etc.) still have to point *somewhere*, and that somewhere must not be addressed in a C-machine style! symbols should point to Lisp memory (via
☝︎☟︎☟︎ a111: Logged on 2017-11-14 11:22 spyked:
http://btcbase.org/log/2017-11-13#1737268 <-- this. ftr, current
adalisp prototype (not-yet-published and thus yet-vapourware!) represents "pointers" as indices in a statically-allocated array.
mircea_popescu: trinque a perhaps even workable alternative would be,
adalisp.