HP3000-L Archives

February 2001, Week 2

HP3000-L@RAVEN.UTC.EDU

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Stan Sieler <[log in to unmask]>
Reply To:
Stan Sieler <[log in to unmask]>
Date:
Thu, 8 Feb 2001 13:50:12 -0800
Content-Type:
text/plain
Parts/Attachments:
text/plain (47 lines)
Re:
> in the SYSINTR.PUB.SYS file.  The Gnu compiler doesn't do this, you have to
> still have four fields that I don't understand.  Is this file format
> documented anywhere?

No.

We tried to get the file format documentation back when we first started
writing the SPLash! compiler.  We were, however, given information on how to
call some routines (which appear to be in XL.PUB.SYS) to access it:

   iclose
   igetparminfo
   igetprocinfo
   iopen
   iprintim

(We aren't allowed to pass on that documentation, sorry)

We were told that there was no way to *add* information to an intrinsic file...
but we noticed that the documents were missing pages, and that some of the
documented errors were things like "attempt to add intrinsic to file failed" :)

Another thing you can do is say "hey, I don't need no steenking documentation",
and do the following:

Create file FOO with:

   $buildint 'sysintr.pub.sys'$
   $listintr 'paslist'$
   program a; begin end.

Then:

   :file paslist; disc=100000
   :pasxl foo,,$null
   :save paslist

And you'll have a readable ASCII file with all of the intrinsics and their
parameter information.

You could repeat the process for the other intrinsic files (e.g.,
AIFINTR.PUB.SYS)

Stan Sieler                                           [log in to unmask]
www.allegro.com/sieler/wanted/index.html          www.allegro.com/sieler

ATOM RSS1 RSS2