Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.lang.postscript > #1579

Re: xpost3 current challenges: a hickup

Show all headers | View raw

On Sunday, June 9, 2013 12:38:27 AM UTC-5, luser- -droog wrote:
> PLRM, 2ed, 7.2 Encoded User Names
> 
> [...]
> 
> 
> 
> The meaning of a given user name index is local to a specific PostScript
> 
> execution context—precisely, to a context’s local VM. If several contexts
> 
> share the same local VM, a user name index defined in one context
> 
> may be used in another context. In this case, it is the application
> 
> programmer’s responsibility to synchronize execution of the contexts
> 
> so definition and use occur in the correct order.
> 
> 
> 
> Entries placed in the user name table by defineusername accumulate
> 
> during the lifetime of the context’s local VM; they do not obey save and
> 
> restore, and they cannot be removed or replaced. These restrictions are
> 
> intentional: they permit the Client Library to manage user name definitions
> 
> without understanding the semantics of the PostScript language
> 
> program being generated.
> 
> --------------------------
> 
> 
> 
> So, I've got to move my names from global-vm to local-vm. And the operator table probably doesn't need to be in global-vm, either, since it cannot be bound to a name object like I'm doing now (In addition to the systemdict:name->operator binding, I put a copy of the name-index in the operator object itself). 
> 
> 
> 
> So this'll require some re-design.

I separated names into global and local banks.
Finding all the places that cooked up name objects
was pretty painful. After a week of debugging, it
runs (test.ps) again. 

Back to comp.lang.postscript | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread

Thread

xpost3 current challenges luser- -droog <mijoryx@yahoo.com> - 2013-05-04 21:59 -0700
  Re: xpost3 current challenges luser- -droog <mijoryx@yahoo.com> - 2013-05-05 21:39 -0700
    Re: xpost3 current challenges luser- -droog <mijoryx@yahoo.com> - 2013-05-10 22:53 -0700
      Re: xpost3 current challenges luser- -droog <mijoryx@yahoo.com> - 2013-05-12 21:49 -0700
        Re: xpost3 current challenges: a hickup luser- -droog <mijoryx@yahoo.com> - 2013-06-08 22:38 -0700
          Re: xpost3 current challenges: incorporating scanner reveals bug of omission luser- -droog <mijoryx@yahoo.com> - 2013-06-24 00:48 -0700
            Re: xpost3 current challenges: incorporating scanner reveals bug of omission luser- -droog <mijoryx@yahoo.com> - 2013-07-22 03:33 -0700
              Re: xpost3 current challenges: incorporating scanner reveals bug of omission luser- -droog <mijoryx@yahoo.com> - 2013-07-22 03:50 -0700
          Re: xpost3 current challenges: a hickup luser- -droog <mijoryx@yahoo.com> - 2013-08-17 11:34 -0700
  Re: xpost3 current challenges luser- -droog <mijoryx@yahoo.com> - 2013-07-23 01:02 -0700

csiph-web