Subject: | |
From: | |
Reply To: | |
Date: | Tue, 28 Mar 1995 11:53:13 EST |
Content-Type: | text/plain |
Parts/Attachments: |
|
|
On Tue, 28 Mar 1995 10:02:03 -0500 Tony B. Shepherd said:
>In article <[log in to unmask]>,
> "Dr. Ferenc Nagy" <[log in to unmask]> wrote:
>] Subject: Re[2]: Hidden intrinsics. Who knows the BUILDINT?
>] Hi John:
>] > SPLINTR.PUB.SYS. I think there is a program needed to "compile" it.
>] > Look in your segmenter manual. I'm at home right now, and don't have any
>] > docs handy.
>] I have found the BUILDINT.PUB.SYS program which listed and rewrote the
>] SPLINTR file but I have not found yet any documantations about it.
>
>There is a corner of my basement where even I am reluctant to go. That,
>I'm afraid, is where my SPL manual is. If you have an SPL manual,
>BUILDINT is documented in it. Good luck - and make a copy first! :-)
Why Tony, you mean the SPL manual is no longer a permanent appendage? :-)
BUILDINT takes SPL procedure declarations as input and creates/updates
an intrinsic declaration file. By default it reads $STDIN and lists to
$STDLIST, maintaining the file SPLINTR. The formal file designators
are INTDECL, OUT, and SPLINTR respectively.
I have used this once in my life to create a custom SPLINTR file (in
SPL you can reference several SPLINTR files, don't know about Pascal)
but I've never tried to update or amend SPLINTR.PUB.SYS.
There are control commands $PURGE (removes all entries),
$REMOVE (remove following entries),
$BUILD (add subsequent entries).
It isn't clear if you specify an existing intrinsic file if it will
simply append (hopefully) or overwrite the existing file, so be sure
to keep a copy of the original SPLINTR.
Jeff Kell, [log in to unmask]
|
|
|