libera/#sicl - IRC Chatlog
Search
14:36:29
scymtym
the second item in the list following "A description of slot-options follows" in http://www.lispworks.com/documentation/HyperSpec/Body/m_defi_5.htm#define-condition looks like a TeX error, right? the postscript output also has a single bullet in the middle of an otherwise definition-style list
15:30:11
scymtym
the ide integration and improved CLIM browser make we want to add stuff again, though :/
15:33:11
beach
I keep thinking of the IDE. There are so many components that exist. If I could just think of a good way to compute indentation, then I think a demo version could be made.
15:36:37
scymtym
from my perspective, there is also a big chunk of unsolved issues in the architecture domain. in particular for integrating early compilation stages and environment maintenance with the incremental parsing. also showing and updating errors and analysis results in a sensible manner
15:36:59
scymtym
but i guess i have prototype-quality solutions for some of those so a demo could be in reach
15:37:43
beach
Right, and we have different ideas there it seems. I see the use of Cleavir/Clostrum/Trucler.
15:39:56
scymtym
right. at least for prototyping i wanted environments that can easily store arbitrary information (current package, information pertaining to the current readtable, etc) rather than something tailored to the language-level Common Lisp environments
15:40:10
beach
It would be like creating Cleavir-based compilers for existing Common Lisp implementations, except that there would be no pressure to generate fast code.
15:40:57
scymtym
there is also the question of whether the ordinary compilation stages should be adapted to work with non-CL:SYMBOL symbols or not
16:06:56
beach
Good progress today with code generation. There are some instructions left to implement, but I don't know exactly how many. A small number I think. Most instruction have been a matter of defining another method on a generic function.
16:07:02
beach
But a few minutes ago, I ran into the SAVE-VALUES-INSTRUCTION and I thin that one should result in a named call, so it will be a bit more involved to implement. I am not going to attempt that this close to dinner time.
16:07:10
beach
There are also some Cluster instruction descriptions missing, in particular LEA. But I think we are getting close to generating code.
16:07:11
beach
After that, there is the primitive call-site manager to implement, and also to write bytes to the simulated heap at the end of bootstrapping.
16:10:20
beach
scymtym: Also, with only Eclector + indentation + what you do with "simulated" environments, the analysis is better than what SLIME can do, so one could start with something like that, and then improve by adding more passes to the analysis.
16:10:43
beach
scymtym: What I am trying to say is that it is not necessary to do a full semantic analysis from the start.
16:13:18
scymtym
beach: yes, full analysis is not required, but i would like to start at a level where we know the meaning expressions and symbols in particular based on the surrounding forms