Larry Masinter comments

Results 717 comments of


                                            Larry Masinter

sort out additional LOOPS resources from envos

Now in the lmm-loops branch in the Interlisp/loops repo -- a raft of Loops documentation. Needs to be vetted and sorted out. Look in the "doc" and "test" folders and...

sort out additional LOOPS resources from envos

https://github.com/Interlisp/loops/pull/13

CLEANUP should produce DFASL or LCOM consistent with what's already there and/or what was previously loaded

they emit different code; we should run the benchmarks with different compilers

CLEANUP should produce DFASL or LCOM consistent with what's already there and/or what was previously loaded

My only concern is that SAMEDIR might interfere with a working style where users want to treat the distribution as read-only, and store updates in their project directory. I wasn't...

CLEANUP should produce DFASL or LCOM consistent with what's already there and/or what was previously loaded

I've been remiss about not gathering together documentation about changes we've made to the default full loadup. I think we need to do that I'm not sure how / where...

CLEANUP should produce DFASL or LCOM consistent with what's already there and/or what was previously loaded

I thought this was fixed, but the other day I did a ED(MEDLEY-INIT-VARS) which did a LOADFROM(LOADUP-LISP PROP) when I did a CLEANUP it made a DFASL rather than LCOM...

CLEANUP should produce DFASL or LCOM consistent with what's already there and/or what was previously loaded

check out internal/library/MULTI-COMPILE.

CLEANUP should produce DFASL or LCOM consistent with what's already there and/or what was previously loaded

I want to get to the place where we can compile everything, starting from 'starter.sysout'. we're not far from being able to do that. Then we can .gitignore *.LCOM *.DFASL...

CLEANUP should produce DFASL or LCOM consistent with what's already there and/or what was previously loaded

both il:load and cl:load can load either. Why don't we settle on a single file extension (.dfasl? .ilc? whatever) and reduce the complexity of loading?

CLEANUP should produce DFASL or LCOM consistent with what's already there and/or what was previously loaded

DOFILESLOAD (called by FILESLOAD, which is what implements the FILES Interlisp filepackagecommand) is what we use to load the appropriate LCOM or DFASL file. I think we've eliminated the files...