Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!mailrus!cs.utexas.edu!uunet!portal!cup.portal.com!Sullivan
From: Sullivan@cup.portal.com (sullivan - segall)
Newsgroups: comp.sys.amiga
Subject: Re: An Emulator for the Amiga
Message-ID: <24887@cup.portal.com>
Date: 10 Dec 89 21:25:41 GMT
References: <13259@merrimack.edu> <21427@usc.edu>
  <4287@eagle.wesleyan.edu> <21476@usc.edu> <4386@eagle.wesleyan.edu>
  <24875@cup.portal.com>
Distribution: na
Organization: The Portal System (TM)
Lines: 22

>
>Speaking from several years' experience with VT240's in both ReGIS and
>Sixel, believe me, ReGIS alone is Godawful complex.  There are commands 
>and subcommands and options and suboptions and several levels of save/restore
>for dozens of variables; bitmap manipulations and masks and polygon fills and
>arc-splining and text and macros...  Whew.  A terse, two-lines-per-command 
>DESCRIPTION of ReGIS commands, alone, comes to about five or six pages just 
>in the "reference card."  It's more like FORTY pages in the programmer's 
>manual...

Forty pages?!? That is nothing.  Look at a tektronix manual some time. 
I've only played with the ReGIS subset which is implemented on the digital
GIGI, but it was much less complex than say, a basic interpreter.  Probably
the most complex part of ReGIS is that you can specify the same command
several different ways.  Rather than hardcode the meaning of each command
it would be neccessary to interpret them.  Still I can't believe that there
aren't any companies out there that are willing to do this. 

...I just flipped through the GIGI manual.  The full command descriptions
are in chapter 12 which is only 25 pages long...

-ss