freenode/#sicl - IRC Chatlog
Search
9:24:26
beach
In less than an hour, my favorite coauthor will come over for lunch, so I'll be a bit busy for the next few hours.
9:45:30
beach
Technically yes, but she has been largely unable to do any useful work for quit some time. She is too busy with other stuff. :(
9:46:16
beach
So I need to think about either finding someone else to work with, or take the time to do it myself.
14:47:12
beach
scymtym: It looks good. Am I right that, in order to use it, I would handle the specific conditions, pop the top of my explicit stack of pending parse results and create a specific one according to the condition, and then invoke the recover restart?
15:01:34
beach
scymtym: You seem to have all the code that is required for parsing Common Lisp in a text editor, and you seem to have a better system than I do for computing indentation. So I have a suggestion. It is fine with me if you ditch all the contents in the Syntax/Common-Lisp directory of Second Climacs and replace it with yours. It is only a bit more than 2k lines of code. And I am sure your code is smaller and better anyway.
15:03:05
beach
scymtym: Alternatively, you can ditch all the rest as well. That's just another 3k lines. And, while I did my best to make it modular, I think I overdid it, so I was not that happy with the result anyway.
15:04:36
beach
scymtym: Plus, at this point, you are more familial with McCLIM than I am, so I am sure you would do a better job on the GUI code as well.
15:05:07
beach
scymtym: I am not particularly attached to my code. I just want to see this thing done.
15:07:39
beach
I have no plans to work on it for the next few months, though I may get bored with SICL and do something.
15:09:21
beach
I know that scymtym is working on a few pieces of the puzzle, as is obvious from his demos, but I also know that he is unwilling to announce public commitments to specific results.
15:10:30
ck_
Okay, thank you. I just wondered whether there was some grand plan with dates and everything.
15:10:42
beach
Another piece of the puzzle will require the first passes of Cleavir, namely the incremental analysis of the code in a Second Climacs buffer.
15:11:43
beach
So for the Cleavir part, I need incremental first-class global environments, which I haven't implemented yet.
15:12:19
beach
And It is still unknown whether Cleavir performance is good enough to handle this stuff.
15:12:57
beach
And the conditions that Cleavir signal would have to be turned into data that Second Climacs can present to the user.
15:15:17
ck_
I feel hurt on the performance-oriented-personality side :) "... but I already _know_ emacs"
15:16:36
beach
I would still use it for most other things, at least until Second Climacs acquires most of the other features I use in Emacs.
15:17:52
beach
What I am hoping is that the accuracy of the analysis will be so good that it will be irresistible. If that happens, a lot more contributions will happen.
15:18:44
beach
Plus, performance will be much better, provided a decent Common Lisp compiler is used to compile the code.
15:19:48
beach
And I use better data structures than Emacs does. The buffer is better for instance. And the Common Lisp parser does not use regular expressions.
15:21:20
beach
So the plan for Second Climacs seems clear. I am a lot more worried about Clordane because it will require support from the implementation that I am convinced the maintainers of existing implementation won't be willing to work on.