I haven't run into this before in myself, but this line from the NEWS
file in guile repository seems like a good lead:
"Previously statprof would show strings like "anon #x1234" for primitives
written in C."
It's in the section for changes new to 3.0.3 so if you're on 3.0.2 or
below then
On 2/1/24 16:16, M wrote:
> If you are going to reify variables, I would propose boxes instead, which
> simply
> hold a single value and hence are have very straightforward semantics and are
> very close to the semantics of variables.
Thanks for bringing that up, I was previously unaware of
Hi Daniel,
> I think this has something to do with compilation indeed. More specifically,
> it is caused by cross module inlining [1]. You probably need to declare your
> env module as not declarative by setting #:declarative? to #f inside the
> define-module form of env. I think the compiler
It's also worth mentioning that a "lispier" way of doing this is to use
parameters, described in "6.11.2 Parameters". I get the impression that
you were asking this more for curiosity about how the language
implementation works than to solve a problem, but I might be wrong in
that assumption
On 1/23/24 05:37, Mortimer Cladwell wrote:
> When I run the above I get as output:
>
> "varB post cond: B"
> "varC post if: C"
> "varA in main: A"
> "varB in main:"
> "varC in main: C"
>
> Why can I reset the variables with both 'cond' and 'if' in env.scm, but
> only the variable reset with 'if'
Is there an RSS or Atom feed for Spritely news? I don't see one on the
web page.
