[racket] getting some weird toplevel values from zo-parse

On Tue, May 24, 2011 at 2:37 PM, Matthew Flatt <mflatt at cs.utah.edu> wrote:
> I don't remember whether it was me or someone else, but it's fixed in
> the latest docs:
>
>  Represents a “prefix” that is pushed onto the stack to initiate
>  evaluation. The prefix is an array, where buckets holding the values
>  for toplevels are first, then the buckets for the stxs, then a bucket
>  for another array if stxs is non-empty, then num-lifts extra buckets
>  for lifted local procedures.


Ok, thank you!  That solves that mystery.