log
17 entries in 0.403s
mircea_popescu: spyked evidently, if adalisp isn't tabletop systems engineering, then what is it.
a111: Logged on 2018-07-02 16:52 mircea_popescu: spyked re http://thetarpit.org/posts/y04/074-adalisp-prototype.html what if anything do you plan to do re memory management ? gc in particular, but not just.
a111: Logged on 2018-07-02 21:25 mod6: spyked: hey! pretty neat-o adalisp here. I tried it out, was able to build. I did get one error in the test.scm, any thoughts? http://p.bvulpes.com/pastes/wXcA6/?raw=true
mod6: spyked: hey! pretty neat-o adalisp here. I tried it out, was able to build. I did get one error in the test.scm, any thoughts? http://p.bvulpes.com/pastes/wXcA6/?raw=true
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...
mircea_popescu: spyked re http://thetarpit.org/posts/y04/074-adalisp-prototype.html what if anything do you plan to do re memory management ? gc in particular, but not just.
deedbot: http://thetarpit.org/posts/y04/075-adalisp-prototype-ii.html << The Tar Pit - The return of the lost son of the father of adalisp, now in a genesis
asciilifeform: oh hey the adalisp
deedbot: http://thetarpit.org/posts/y04/074-adalisp-prototype.html << The Tar Pit - An early Lisp scriptlang prototype in Ada
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.
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.