Thanks Iain, great observations and info. Yes, we’ve read s7.html many
times and will continue to do so. There’s a lot of great info there!
(We’ve found many of the included scm files are also good sources
too.)
FYI, we’re looking at adopting R7RS more as a future-proofing strategy
than “we
Do I understand you correclty that the patch I
implemented break some assumption of your code
In general, yes. I'd have to read through the
code -- I glanced at it a few months ago, but
can't remember any details, except that it struck
me as written for Guile 1.8? and perhaps
awkward for s7
Dear Bill,
thanks for the remarks. Do I understand you correclty that the patch I
implemented break some assumption of your code. Is there a way to be sure I'm
not introducing any bug?
Best,
Max
> On 17. Jan 2022, at 21:13, b...@ccrma.stanford.edu
> wrote:
>
> Currently, s7's optimizer
Environments come and go at an amazing pace
That's why I suggest to only build a hash table only after a certain
number of accesses.
-E
___
Cmdist mailing list
Cmdist@ccrma.stanford.edu
https://cm-mail.stanford.edu/mailman/listinfo/cmdist
Another idea is inline caching...
And probably better than a hash-table, but it's yet
another layer in an already complicated process.
I might try that just to see what happens --
thanks for the suggestion!
___
Cmdist mailing list
Why not maintain a hash table whose values are offsets into the flat
environment?
Then it's a cheap branch or two on lookup to see: 1) is there a hash
table;
2) should I build one (is the env big enough, and have there been
enough lookups).
I call that serious overhead. Environments come and
Another idea is inline caching...
On Mon, 17 Jan 2022, Elijah Stone wrote:
On Mon, 17 Jan 2022, b...@ccrma.stanford.edu wrote:
Currently, s7's optimizer sometimes depends on the position of the
variables in environments, so your change is only safe if the optimizer
gives up. Since the order
On Mon, 17 Jan 2022, b...@ccrma.stanford.edu wrote:
Currently, s7's optimizer sometimes depends on the position of the
variables in environments, so your change is only safe if the optimizer
gives up. Since the order matters, a hash-table lookup is unlikely to
work without some serious
Thanks for the observations -- I'm glad s7 has
worked out reasonably well. On your questions:
1) would it be possible to have lookup_from implemented via some hash
table...?
Alternatively, can our patch be made into the official version?
Currently, s7's optimizer sometimes depends on the
Dear all,
integration of S7 in the TeXmacs document editor (www.texmacs.org) has been
quite successful so far. You can grab the associated development branch here at
github
https://github.com/texmacs/texmacs/tree/wip_s7
you will need Qt 4/5 and some other libraries to compile it. Some
The with-exception definition in r7rs.scm probably should be
(define (with-exception-handler handler thunk)
(catch #t thunk (lambda args (apply handler args
The define-library code dates from the days (years ago)
when s7's define-macro returned the symbol rather than
the value. Also, I
Hi Rudolf, Bill would be the person to address this better than me, but I
think the Egghead team should read through the s7.html page pretty closely
to see if s7 is a good fit. It's pretty clear in there that there is
*limited* R7RS compatibility, but that s7 is not R7RS and nor is that a
stated
12 matches
Mail list logo
