∂20-JUL-74  2037		MAP,RF
 IN SAIL, WHAT SHOULD I ← (J ← 3) + (J ← 4)
 RETURN FOR I?  I HAVE THE NASTY FEELLNG IT GETS 8.



∂28-JUN-74  2013		network site CMU
 ***** FTP mail from [A700SA00] (SAIL)
 To:	SAIL types
 From:	ERMAN@CMU-10
 Re:	mods to GOGOL, IOSER, and PARSE
 Date:	28-Jun-74
 
 
 I have made some fairly trivial fixes to error handling, but
 would like to see them get into your S,AIL files so they
 won't get lost.
 The fixes are described below.  I'm sure that
 none could be objectionable.
 
 The sources can be found on CMU,AIL as follows:
 
 PARSE.PRT -- the change for PARSE.
 IOSER.PRT -- contains replacements for pages 6,7,&9 of IOSER.
 GOGOL.PRT -- gives the three changes for GOGOL.
 
 =C2=	[GOGOL/32] LDE (28-Jun-74)
 	Allow call SOS in RPG mode if no file-name specified.
 	(Totally within CMUSW.)
 
 =C3=	[GOGOL/29, PARSE/22] LDE (28-Jun-74)
 	Under NOSTANFO, when printing error messages, translate
 	under-bar into "!" and not-equals into "#".  This is much
 	better for non-stanford terminals (although could be
 	made more general).
 
 =C4=	[IOSER/6,7] LDE (28-Jun-74)
 	Allow null PPN within [] and allow nulls within PPNs, in
 	FILNAM.  (The second occurs frequently at CMU since CVSTRs
 	are often done on PPNs.)
 
 =C5=	[IOSER/9] LDE (28-Jun-74)
 	Allow lower-case "r" response when device not available in OPEN.
 
 =C6=	[GOGOL/31] LDe (28-Jun-74)
 	Allow lower-case file names when specifying an "E" response
 	in an error message.
 
 
∂25-JUN-74  0124		THE,JRL
 Ralph has complained about the fact that SAIL does not reduce
 CORE size between compilations.
 Also when we have $PDLOV cause an pdlov there is no indication
 as to which stack really overflowed. E. g in procedure entry
 sequence.
 		Add	p,[xwd mumble, mumble]
 		skipl	p
 		jsp	15,$pdlov

 $pdlov causes an overflow with 14 as stack pointer. User gets
 no indication that problem was really with p.


∂24-MAY-74  1125		NET,GUE AT TTY122 : C.BACON @  network site NBST
 SAIL COMPILER BUG:
 THE FOLLOWING SEQUENCE--
 BP ← POINT (6, FOO, -1);
 FOO ← GEORGE;
 IDPB (0, BP);
 GEORGE ← FOO;
 --  RESULTS IN NO APPARENT CHAGE TO FOO OR GEORGE.
 REASON SEEMS TO BE THAT SAIL 'KNOWS' THAT FOO IS STILL COPIED
 IN AN AC, AND DOESN'T NEED TO   MOVE  AC,FOO   BEFORE MOVEM'ING.
 OH, WELL, I CAN ALWAYS GET AROUND IT.
 
 FROM C. BACON, N.I.H. DCRT.  BETHESDA, MD.  INITIALS CRB.
 

 
∂25-MAY-74  1000		1,RS
 RUSSELL,
 	On your desk I have left a listing of SAILOW.SRC.
 it shows the effects of what we did.  As far as I can tell,
 all of the globals that are linked to from the user's program
 are ok.  P.S.  What happens when users declare things EXTERNAL
 and link to them when they are not in the HERE table -- it
 is just the user's own fault for being so dump??
 			bob

∂01-MAY-74  0221		1,JMG
 I seem to get "DRYROT AT EFORM" and cure it without any seeming rationality.
 If this is of further interest, mail me a mssg and I'll point to the file.
 				- jmg.

∂29-APR-74  1244		network site CMU
 ***** FTP mail from [A700SA00] (SAIL)
 CMU bug report =B8=.   LDE 29-Apr-74
 	Bug fix #RN is not complete -- see short file
 	PROTAC.SAI[CMU,AIL] or [A700SA00] for a test case.
 	It complains about protecting AC's again.
 
∂24-MAR-74  0940		network site CMU
 ***** FTP mail from [A700SA00] (SAIL)
 CMU bug report  =B5=.  LDE 24-Mar-74.
 	Can get "illegal real constant" errors inside an IFCR FALSE
 	with a construction like "..".  See IFCRBG.SAI[CMU,AIL].
 
∂19-MAR-74  1125		network site CMU
 ***** FTP mail from [A700SA00] (SAIL)
 00100	RUSS AND OTHERS,
 00200		WHAT IS THE STORY WITH "A" AS AN ERROR RESPONSE  THE CODE
 00300	LOOKS LIKE IT MEANT TO INCLUDE "A", BUT THERE IS A CAILE A,15 THAT
 00400	ONLY LETS LINEFEEDS THROUGH (GOGOL 7400/27).  USING "A" HERE SETS
 00500	THINGS UP SO THAT ONE GETS THE EFFECT OF LINEFEED, BUT ONLY AFTER
 00600	BEING COMPLAINED AT, AND HAVING TO TYPE SOMETHING ELSE BACK FIRST.
 00700	WHAT'S THE CASE THERE?
 00800					PADDY

∂15-MAR-74  1654		network site MAXC
 Date: 15 MAR 1974 1656-PDT
 From: SPROULL at PARC-MAXC
 Subject: Another SAIL bug
 
 - - - -
 I have just received information from NIH to the effect that SAIL 
 crashes the new release of 5.07/6.01 (DEC system).  The rason,
 it appears, is that the first few locations of the high segment
 (the vestigial job data area) are all -1.  Glenn Ricart reports
 that making them '0'  (i.e. the first 8 locations in the high seg)
 cures the problem altogether.
 
 I think this should be put in.
 		bob
 -------

∂15-MAR-74  1652		network site MAXC
 Date: 15 MAR 1974 1654-PDT
 From: SPROULL at PARC-MAXC
 Subject: SAIL BUG
 
 - - - -
 The following program fucks up looking for a global value.
 The problem is that the 'move 2,1(2)' at d+2 should be 
 (I think....) a 'move 2,(2)' to look back up the stack.
 See what you think.
 
 00100	begin "bug"
 00200	procedure a(integer i;reference procedure p);
 00300	p(i);
 00400	
 00500	procedure t(integer i);
 00600	begin procedure d(reference integer i);
 00700		outstr("i="&cvs(i));
 00800	
 00900	a(i,d);
 01000	end;
 01100	
 01200	t(22);
 01300	end
 
 
 By the way, I would appreciate acknowledgement of my bug reports
 so that II know that they have been received.
 
 Good luck.
 			Bob
 -------
 


∂11-MAR-74  1957		network site CMU
 ***** FTP mail from [A700SA00] (SAIL)
 Continuing bug report.  CMU LDE 11-Mar-74
 	There is still a problem with expanding string space in
 the compiler.  Unfortunately, we only seem to get it in our
 humongous HEARSAYII compilations, which use about 20 or 25
 different source files.  Our compiler has all the purported bug
 fixes for this -- in fact we brought over a complete set of
 source files from S,AIL within the last two weeks.  If we find
 a more compact program that pokes at it, we'll ship it over
 and let you know.  If someone there gets ambitious and wants to
 poke at our thing over the net, we will be glad to give assistance.
 I suspect that DCS has some ideas on what the problem might be
 (see his message along with a bug that he set up for it -- about
 QF, I think).
 		cheers,
  
∂06-MAR-74  1144		CMU,AIL
 How much of feats if honest?  Specifically, %AG, which is in the files, but
 has no OK, and isn't in the documentation.
 PB01

∂5-MAR-74  1040		network site CMU
 CMU BUG REPORT, WITH FIX.  LDE=B2=	[GOGOL/46] LE03 5-Mar-74
 	In STRNGC, when releasing old string spaces, DCS was accessing
 	the header of the space after he released it (with a CORREL) --
 	this caused ILL MEM REF when the core happened to have really
 	gone away.  Fix required no more code.
 
 RELLUP:	MOVEI	B,-.HDRSIZ(A)		;Release any spaces which are
 ;;=B2=	LDE CMU 5-MAR-74	BETTER NOT ACCESS IT AFTER IT GOES AWAY
 ;	PUSHJ	P,CORREL		; apparently no longer necessary.
 ;	SKIPE	A,.NEXT(A)
 ;	 JRST	 RELLUP
 	MOVE	A,.NEXT(A)
 	PUSHJ	P,CORREL
 	JUMPN	A,RELLUP
 ;;=B2=
  
∂05-MAR-74  0804		CMU,AIL
 PEOPLE:
 	IF YOU ARE BRINGING OR HAVE BROUGHT UP A SAIL MANUAL UPDATE, I
 WOULD APPRECIATE KNOWING ABOUT, AS I AM DOING THE SAME.  SEND MAIL TO
 BANWELL OR SAIL ON THE CMU/B.
 				PB01
 
∂25-FEB-74  1525		R,AJT
 HOW ABOUT A BETTER ERROR MSG FOR "APPLY(ITM,LST)"
 (NEED DATUM(ITM) HERE).   RHT
 

∂22-FEB-74  1034		network site CMU
 Poke from CMU re two bugs that were reported and seemingly ignored:
 (LDE 22-Feb-74)
 
 =A1=
   This is the fact that once a break table is put into "K" (convert
 to upper case) mode, there is no way to reset it.  The fix is simple
 enuff:
   Add a new mode, "F" (Full character-set mode), which is the
 "default" and add the following three lines of code needed:
 
 [IOSER/25]
 1)  change  	XWD NOLINS,ILLSET	;n,,-
     to		XWD NOLINS,LCASE	;n,,f
 
 2)  add at the bottom of the page (following UCASE code):
 	LCASE:	MOVSS  B
 		ANDCAM B,BRKCVT(USER)
 		JRST  RESTR
 
 
 
 =A7=
 	At SGSORT, it is not(!) checking for null strings, thank you.
 It  used to  before DCS  put in dynamic  string space.  Some run time
 routines do create null strings  that are not marked as constants and
 which do not have legal addresses.  (In particular, Realscan seems to
 do this.) In addition, the old manual used to state that if the count
 is zero, then the address is ignored. In any case, something needs to
 be done to this.
 
∂05-FEB-74  1412		THE,RHT
 REG SENT ME SOME BUGS IN THE MANUAL.  THE MESSAGES WERE SENT TO MSGLOG[S,AIL]
 

∂5-FEB-74  0816		network site CMU
 CMU Sail bug report (low priority)	=A6=	LDE 5-Feb-74
 	A NEEDNEXT block with no NEXT in it gets a dryrot at FBOUT.
 	(Joe Newcomer bug.)
 
∂29-JAN-74  0746		CMU,AIL
 THE FIX FOR CMU =A1= IS:
 	XWD	NOLINS,LCASE	;N,,F
 IN PLACE OF WHAT IS NOW 3000/25 IN IOSER, AND
 	LCASE:	MOVSS 	B
 		ANDCAM	B,BRKCVT(USER)
 		JRST	RESTR
 AFTER UCASE, AT THE END OF /25 IN IOSER.   PADDY

∂28-JAN-74  1539		network site CMU
 ***** FTP mail from [A700SA00] (SAIL)
 00100	BUGS IN IOSER
 00200		=A1=: ONCE TURNED ON, UPPER CASE CONVERSION CAN'T BE TURNED
 00300	OFF.  USE OF LCASE GIVES AN ERROR MESSAGE OF UNDEFINED.  THIS IS ON
 00400	PAGE 26 OF IOSER.
 00500		=A5=: WHEN SIMIO INDICES WERE CHANGED BACK TO THEIR OLD
 00600	ORDER, THE USBTST TABLE WAS NO LONGER CORRECT.  OUR FIX WAS TO ADD
 00700	A DUMMY WORD BETWEEN THE TWO ENTRIES.   LE03 & PB01
 00800	
  
λ