🚀 go-pugleaf

In article <19920@usc.edu>, papa@pollux.usc.edu (Marco Papa) writes:
> The 2.0 spec, just finalized and posted in bet on BIX, adds two functions that
> allow "watchin" the comm line for "special character sequences" (like the ones
> for Zmodem and CI$ autodownloads), support for DoubleTalk protocols, and
> external terminal emulations (XEMs vs XPRs).

Hmm .. Sounds great ! Is is the same spec. that may be found on Fish 247 ?
I can't get to Bix from France, but now that we have a CBM BBS for
developer support in France (also in other European countries I believe),
I think it would be a good idea that this kind of documents should be 
forwarded regularly to these sites.
I'm not sure what the exact procedure should be, but maybe we can work it 
out. 
In my opinion, the whole thing (VLT, XPRs) is really good work, and should be
advertised. I'm anxious to see if XEMs make sense in a BBS context, as sure 
as XPRs do !


> [......] The XPR link-time library is a 'sample' for comm 
> program writers.  The 2.0 spec cxlearly mention that if you want to 
> do what you describe of want separately selectable XPRs and XEMs you have 
> to set up other XPRxxxxBase pointers, one for each of the "concurrent"
> things you want around.  [...]

Ok I buy this solution. The library solution would introduce more stubs,
and is in fact too heavy for such a light work.
There are already so many "interfaces" because all specifications are 
based on parameter passed in registers, and most of the code is written 
in C.

> |Comments ? Other solutions ?
> You got them.
> -- Marco Papa 'Doc'

Thanks for these explanations. Thanks also to others who followed the
discussion.
-- 
*- Francois Rouaix                 //       We are all prisoners here,       *
*- rouaix@inria.inria.fr         \X/           of our own device             *
*- SYSOP of Sgt. Flam's Lonely Amigas Club. (33) (1) 39-55-84-59 (Videotex)  *
Disclaimer: Opinions expressed are my own, not those of my employer.