Hi -- Okay. I'm going to ask for my first lifeline. :) I'm tracing through
some arcane stuff indeed. Everything is going along swimmingly. I get to the
word new-key@, which at its start wants to execute [ array 2dup hash@ 0 f
(new-key@) ] with the keep combinator. All good so far. array
In the listener, if you run this code:
IN: scratchpad clear
IN: scratchpad value key associate
Then step over to [ set-at ] keep
If at this point you just keep stepping into things, you should do a deep
dive into all the parts, including the 4 slot { array } declare which
should give
Wow. Great, John! Thanks. This should keep me at bay for a good while.
From: mrj...@gmail.com
Date: Thu, 16 Aug 2012 08:10:31 -0700
To: factor-talk@lists.sourceforge.net
Subject: Re: [Factor-talk] Any way of making sense of what's in the boot
image?
In the listener, if you run this
Btw, you might be wondering why you can't step into the slot word:
If you look at it, it's a primitive, meaning implemented in the VM C++ code
or a compiler intrinsic:
```
IN: scratchpad \ slot see
IN: slots.private
PRIMITIVE: slot ( obj m -- value ) flushable
```
In this case, I believe it is
So then, John, does that mean that in the [ 4 slot { array} declare ],
that I'm getting the slot named array which is at offset 4 (and then
declaring that to be an array, so as to disable some of the type safety
checks)?
Yes, the hashtable code is written at a bit lower level and thus maybe
Great, thanks.
Sent from my iPhone
On Aug 16, 2012, at 1:11 PM, John Benediktsson mrj...@gmail.com wrote:
So then, John, does that mean that in the [ 4 slot { array} declare ], that
I'm getting the slot named array which is at offset 4 (and then declaring
that to be an array, so as to
The reports of my death are greatly exaggerated - Mark Twain
I'm very pleased to announce the release of Factor 0.95! You can
find download links on the Factor website:
http://factorcode.org
This release is brought to you with over 2,500 commits by the following
individuals:
Alex
