Thursday Oct 12,1978 FQ+3D.8H.53M.53S. COMPLR 834 - JONL -  New command line switch "Y", causes all warning and error messages to appear on the TTY. A summary of conditions for compiler messages appears below.  OBARRAYs revisited: SOBARRAY and COBARRAY, also SREADTABLE and CREADTABLE.  Functional variables are no longer supported. "V" switch is gone. You will have to use FUNCALL if that's what you want. Beware. _________________________________________________________________________  New command line switch "Y", causes all warning and error messages to appear on the TTY. A summary of conditions for compiler messages appears below. The "Y" switch controls the variable YESWARNTTY; if the "T" switch has been specified, it too will set YESWARNTTY on. Default setting for all switches is "off", except "F", "K", "O", and "U". The "U" switch primarily controls the printing of the assembler's commentary into the unfasl file; warning messages and error messages from either the compiler or assembler will be put into the unfasl file (as well as into any file on the list CMSGFILES, which is initially null), and will also be printed on the TTY if YESWARNTTY is non-null. If nothing other than the header gets put into the unfasl file, it will be deleted. If no fasl file is being produced (only the lap file is being generated), then the warning and error messages will be put into the lap file. The format of commentary in the UNFASL file is: 1) A header of three lines with source file name, assembler version number, and compiler version number, and (optionally if available) a line with the date and time of compilation. "'(THIS IS THE UNFASL FOR (fn1 fn2 dev usr))" "'(ASSEMBLED BY FASLAP /nnn)" "'(COMPILED BY LISP COMPILER /nnn)" ";COMPILED ON WEDNESDAY, OCTOBER 11, 1978, AT 12:49 PM" 2) "(COMMENT **** " begins a warning message 3) "(COMMENT **ERROR** " begins an error message 4) " (COMMENT **FASL** " begins a comment from the assembler 5) "(COMMENT " begins users COMMENTs, which are added to the unfasl file switches | warnings | errors | run break-loop | notifications T Y G | to TTY | to TTY | if find errors | to TTY ________________|__________|________|________________|______________ off off off | no | no | yes | no off off on | no | no | no | no off on off | yes | yes | yes | no off on on | yes | yes | no | no on off off | yes | yes | yes | yes on off on | yes | yes | no | yes on on off | yes | yes | yes | yes on on on | yes | yes | no | yes  OBARRAYs revisited: SOBARRAY and COBARRAY, also SREADTABLE and CREADTABLE. SOBARRAY is a global variable which holds the obarray containing the compiler functions; COBARRAY holds the user's functions. It is possible to create a COMPLR that has only one obarray (normally there are two - one for the compiler's functions, and one for the users') if at creation time before fasloading the COMPLR, one does (SSTATUS FEATURE NO-EXTRA-OBARRAY). Both obarray names - COBARRAY and SOBARRAY - are on both obarrays; so it is an easy matter to switch obarrays - just do (SETQ OBARRAY SOBARRAY) or (SETQ OBARRAY COBARRAY) COBARRAY is made current after quitting to LISP toplevel (such as by typing ^G), so that complr functions will not interfere with use of CHOMP. Also CREADTABLE is allied with COBARRAY in the attempt to separate user-specific syntax from the standard LISP syntax. Both names CREADTABLE and SREADTABLE are on both obarrays.