Re: Help understanding how code works (or doesn't)

[Carl Sorensen]

On 9/16/10 4:55 PM, "Neil Puttock" <address@hidden> wrote:

> On 15 September 2010 03:40, Carl Sorensen <address@hidden> wrote:
> 
>> Note that at this point, I haven't changed the value to which I am setting
>> 'measurePosition.  So, can anybody help me see why this code doesn't work?
> 
> It looks like adding the extra iteration step (ApplyContext) delays
> the 'measurePosition setting.  It might be the case that it ends up
> being overridden by the Timing_translator before it's been read by the
> autobeamer.

How would one go about trying to verify this with the debugger?

I get lost once we get past the parsing stage; I know that iteration
happens, but I have very little clue about *how* iteration happens.

> 
> Using an iterator directly seems to work (see attached), but might be
> considered a dubious hack; what do you think? :)

Actually, I like the patch.  I don't think it's a hack.  I think it's a
bigger hack to set context properties in Scheme (when we can't read the
context properties from Scheme).

I'd support pushing it as-is.

Thanks,

Carl