Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!watmath!clyde!bonnie!akgua!sdcsvax!sdcrdcf!hplabs!sri-unix!milne@UCI-750A.ARPA
From: milne@UCI-750A.ARPA
Newsgroups: net.micro
Subject: Re: UCSD P-System: Info needed on GETCMD interface and chain.
Message-ID: <12485@sri-arpa.UUCP>
Date: Fri, 28-Sep-84 23:16:34 EDT
Article-I.D.: sri-arpa.12485
Posted: Fri Sep 28 23:16:34 1984
Date-Received: Mon, 1-Oct-84 04:22:34 EDT
Lines: 31

From:  Alastair Milne 


   The p-System utility DECODE is a very useful tool.  I have used it 
extensively, and would not do without it.  Nevertheless, it can only show 
the interface of a unit which has its interface text included with it.
None of the units in SYSTEM.PASCAL has its interface (or God knows how big 
the system would be).  DECODE is therefore no good for showing them (unless
you want to look at the p-code of the unit itself, which is possible, but VERY
time consuming).

    Another thing only just occurred to me: I believe that GetCmd is just a 
segment procedure within the unit Kernel.  It therefore has no interface, and 
in fact cannot even appear in the Kernel's interface, since units cannot 
export segment routines.

    In any case, the original problem was to get CommandIO's routine 
Chain to chain to system files, and my previous message answered that.

    As a matter of general interest, the interfaces of several units in 
SYSTEM.PASCAL which may be useful for user programs (eg. ScreenOps, 
CommandIO, Kernel, etc.)  are available in a separate library, in case 
a user wants to compile with them.  (At least, this is true of NCI's release
for the IBM, and also of Sage's release, I think.  I don't know about anybody 
else).  The running program then uses the copy in SYSTEM.PASCAL.  I don't 
remember offhand just which units have interfaces available for them.

				Alastair Milne

				Educational Technology Center
				University of California, Irvine