its icon indicating copy to clipboard operation
its copied to clipboard

LIBLSP; RDTAGS FASL needs to be compiled from source

Open eswenson1 opened this issue 7 years ago • 2 comments

The source for this is LIBDOC; RDTAGS BYRON2. However, that file makes a reference to AI:KEN;DECLAR >, So we'll need to update the AI: reference to DSK: KEN; DECLAR > loads AI; KEN; DECLA2 >, which is missing. So we'll need to locate that file and update KEN; DECLAR > to not reference AI;

eswenson1 avatar Mar 24 '18 00:03 eswenson1

Once LIBDOC; RDTAGS > is updated to not reference the AI machine to load KEN; DECLAR >, then KEN; DECLAR > must be updated to not reference AI: KEN; DECLA2. But even with those two changes, the code looks for KEN; GCDEMN, LIBLSP; #PRINT, KEN1;REAMAC. So more files to find.

eswenson1 avatar Jul 15 '18 05:07 eswenson1

Couldn't find the source for KEN; GCDEMN FASL, so I decided to try to use the one in LIBLSP. However, I could not compile LIBLSP; #PRINT RCW3. First, this uses # as a normal syntax character, so I added an (eval-when (eval load compile) (setsyntax #/# 1 43)) to the head of the file. That allowed compilation to get further, but then I ran into all sorts of other errors.

For example, the compiler says this:

;(#1SUPSTACK 0) Obscure format - SETF

(COMMENT **ERROR**  (SETF (#1SUPSTACK 0.) 0.)
                LISP error during MACRO expansion in function #EXPLODEL)
; DATA ERROR - TO PROCEED TYPE $P

But I see no uses of SETF in #EXPLODEL (or macros invoked by it).

The comment at the top of #print RCW3 says:

;-----------------------------------------------------------;
;       -- THIS FILE IS OBSOLETE  --  USE GPRINT --         ;
;-----------------------------------------------------------;

So I'm not sure it is worth trying to get this to build. I suspect this is all obsolete stuff (including RDTAGS).

eswenson1 avatar Aug 15 '18 01:08 eswenson1