TIP: Click on subject to list as thread! ANSI
echo: cis.os9.68000.osk
to: Bob van der Poel 76510,2203
from: Kevin Darling 76703,4227
date: 1991-11-01 20:36:30
subject: #12797-Termcap and Basic

#: 12801 S12/OS9/68000 (OSK)
    01-Nov-91  20:36:30
Sb: #12797-Termcap and Basic
Fm: Kevin Darling 76703,4227
To: Bob van der Poel 76510,2203

Actually, you've mentioned previously the possibility of allocating memory on
the fly.  This seems like the best bet to me.

The first thing the program would run each time would be RUN TERMCAP("Init")
oops I mean RUN Termcap("Init",ADDR(storage))... .  Then each call would
also pass the same storage pointer.

The neat thing is, a program could actually talk to several different types of
terminals at once (!) by simply calling the Init routine with different storage
parms.

The other calls would be normal.. RUN Termcap("InsertLine",ADDR(storage)) and
so on.

BTW, it turns out that Basic/68K does pass the environment onto subprograms, so
one way to get env vars would be to fork a printenv process that was piped back
in for reading.

SOURCE: compuserve via textfiles.com

Email questions or comments to sysop@ipingthereforeiam.com
All parts of this website painstakingly hand-crafted in the U.S.A.!
IPTIA BBS/MUD/Terminal/Game Server List, © 2025 IPTIA Consulting™.