freenode/#sicl - IRC Chatlog
Search
7:13:29
jackdaniel
shka__: how do you imagine library working on a very specific environment implementation to work as a "general library"?
7:43:51
shka__
jackdaniel: i was under the impression that the second climacs is portable, and therefore it would not be "very specific environment implementation"
8:01:39
jackdaniel
beach: do you mean that climacs will maintain its own environment implementation alongside the implementation it runs on, or that climacs will depend on a specific env representation provided by the underlying implementation?
8:07:57
scymtym
the general theme is having portable, reusable modules for the reader, for environments, maybe for symbols and the package system and using those everywhere: in editors, in static analyzers, in SICL
8:09:21
scymtym
beach: i'm doing something similar for tracking (some of the) state that is relevant to the reader such as the current package
8:52:48
beach
shka__: I would have to turn the SICL first-class global environments into a separate library first.
8:57:04
splittist
Which is what the mainstream of editors / IDEs are incorporating (again) these days
8:58:48
splittist
shka__: I think you are correct that the api for using all this functionality is going to be very different, and it will probably take quite some time to work out the best way to present it to extension-writers, as it were
8:59:48
shka__
splittist: further more, you would be able (I think?) to make you program work in a separate env, fork this env, modify the env, rollback the env
9:08:28
beach
I don't think we will realize all the possibilities until we have something to play with.
13:04:47
Bike
RECOVER could probably just be CONTINUE, which is the standard "keep going in a default way" restart
13:04:47
Colleen
Bike: drmeister said 24 minutes, 33 seconds ago: Currently llvm loses a lot of information about local variables at -O3. I thought if at high debug we mark all loads and stores in a function as 'volatile' that this would keep the variable in memory even at high optimization and I would have a hope of pulling it out of the dwarf debug info. There would be a runtime penalty of course. Then when/if llvm's ability to track variables improves we drop volatile.
18:57:33
Bike
https://github.com/robert-strandh/SICL/compare/cst-to-ast-errors?expand=1 here's what i've done so far with the conditions stuff
18:58:05
Bike
i've got it coordinated enough with clasp that normal slime things like compiler notes work, and it'll go to the position of a handler-bind macro form with bad syntax, and such