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

Groups > comp.lang.postscript > #1386

Re: xpost3 current challenges

Show all headers | View raw

On Saturday, May 11, 2013 12:53:31 AM UTC-5, luser- -droog wrote:

> 
> So there appears to be a need for these 3 master tables for the global interpreter state. It doesn't really belong in any of the VM files.
> 
> 
> 
>  -context-table
> 
> [       ] -current-context-id
---^ should've indented this one. There's 3 tables, but 4 'variables'.
> 
>  -global-table
> 
>  -local-table
> 
> 
> 
> this could be stored in yet another memory file. So the complete interpreter state would also be reflected in the disk files:
> 
> 
> 
>  g0.mem g1.mem
> 
>  l0.mem l1.mem l2.mem
> 
>  itp.mem

This is going to involve a bit of redesign of contexts and mfiles, as well as a cool name for the master super-duper data structure that in the darkness binds them. 

But I think I'll keep itp.c pretty much as-is, and the testing main() will for now be the entry-point to the single-process interpreter. The "ghostscript"-mode, if you will. The multiprocessing stuff really needs to be a new module. So it needs a module-name, too. Going by my pattern so far, it should be a 3-letter identifier. "srv" maybe, or ... not coming up with anything else. "srv" it is!

I eventually want to make a "quick-launch" option for itp. But there needs to be some provision for validating a pre-initialized VM file. And depending on the severity of the validation checking, "quick-launch" may be a failure in the end. But it feels like *the thing to do*, you know?

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