Number: 172 Date: 18-Mar-84 16':30':41 Submitter: Sannella.PA Source: JONL.PA Subject: Document place of RDSYS, \OPCODES in loadup Lisp Version: Description: ' Date': 14 MAR 84 06':00 PST' From': JONL.PA' Subject': Changes to FPLUS, FTIMES' To': MASINTER' cc': VANMELLE, LISPCORE^' ' Current loadup attempt from LispCore>Sources dies underneath some FTIMES calls (in function LOGOW, trying to layout the "snail"). I edited LOGOW so that it didn''t do the "hard" case of FTIMES, but now it dies underneath SIN, calling FREMAINDER.' ' Could it be that the UFNs for these guys you changed recently are schrod?' I''ve left the "corpse" on Plaza, which is connected to the terminal in' 1623. It was sort of in a half-way WINDOWworld state, and I called RAID' manually to see what was going on.' ' Maybe one of you could look at it before someone else snatches Plaza.' -----' Date': 14 Mar 84 19':58 PST' From': masinter.pa' Subject': Re': Changes to FPLUS, FTIMES' In-reply-to': JONL.PA''s message of 14 MAR 84 06':00 PST' To': JONL.PA' cc': MASINTER.PA, VANMELLE.PA, LISPCORE^.PA' ' It seems unreasonable to edit LOGOW to fix a suspected bug in FTIMES, doesn''t it?' ' I tried finding any problems with arithmetic in the INIT.DLINIT and haven''t been so far. I will continue with the loadup again and see if I can make it happen again.' -----' Date': 14 Mar 84 20':34 PST' From': masinter.pa' Subject': more on FPLUS, FTIMES' In-reply-to': JONL.PA''s message of 14 MAR 84 06':00 PST' To': JONL.PA' cc': MASINTER.PA, VANMELLE.PA, LispSupport' ' (To': LispSupport, AR for Documentation/Implementors Guide': Document this stuff)' ' I suspect the problem is that the variable \OPCODES is duplicated on more than one file, and that I changed it on one file and not on the other. I dunno where or why the duplication, but am searching.' ' (MORE)' ' I now believe the problem is that \OPCODES got copied to RDSYS during RENAMEFNS(R). It is actually the case that whenever any of a given set of files which RENAMEFNS(R) renames changes, that the rename should be redone.' ' RDSYS didn''t used to be loaded as part of the init process. Another way of isolating the problem is to change the loadup script to' ' (SETQ SYSOUT (MAKEINIT --))' ' (load in RDSYS )' (DLFIXINIT SYSOUT --)' ' i.e., to make sure that RDSYS doesn''t interfere with the MAKEINIT files.' -----' Date': 16 MAR 84 11':36 PST' From': JONL.PA' Subject': Re': opcodes list reconstructed, new loadups on Next>' To': masinter, LispCore^' cc': JONL' ' In response to the message sent 15 Mar 84 01':17 PST from masinter.pa' ' What *was* the problem with the \OPCODES list? Will it still be' a good idea to change the loadup script to do the MAKEINIT first and' then load in RDSYS and call DLFIXINIT ?' Workaround: Test Case: Edit-By: masinter.PA Edit-Date: 13-Jul-84 17':29':16 Attn: Documentation Assigned To: In/By: Disposition: System: Documentation Subsystem: Internal System Documentation Machine: Disk: Microcode Version: Memory Size: File Server: Server Software Version: Difficulty: Easy Frequency: Everytime Impact: Minor Priority: Unlikely Status: Open Problem Type: Documentation Source Files: