perm filename MSGLOG[S,AIL]6 blob
sn#023192 filedate 1973-02-06 generic text, type T, neo UTF8
I fixed up the file of this morning's message (but still have a listing
in case you want to see it) but it still "DRYROTS". The file is
TRY.SAI[G,MJC]. Is there something special I should know about for-stmts?
Mike Clancy
17-NOV-72 1742 G,MJC
A program which I wrote to try to learn a few things (namely SAIL and the
Quam display routines) uncovered a "DRYROT" error. The program is
TRY.SAI[G,MJC], and the error occurred in line 2600. Any suggestions?
Mike Clancy
JAM again. Sorry, it doesn't go away with
an "IF TRUE THEN", only with an "IF FOO THEN"
22-NOV-72 2344 MA,JAM
JAM here bringing to you yet another
insidious SAIL bug. There is a program
BUG.SAI[MA,JAM] which compiles the following
code incorrectly (see page 6 of source file):
BEGIN "FLTO"
REAL ARRAY Y[1:LN+GWIDTH];
*** LOTS OF STUFF ***
END "FLTO";
BEGIN "DPGT"
INTEGER ARRAY BUF[1:5500];
*** MORE STUFF ***
END "DPGT";
The following code appears:
DPGT&DPGT.-6/ PUSHJ P,BEXIT
DPGT&DPGT.-5/ PUSH P,3 ; LOWER ARRAY BOUND???
DPGT&DPGT.-4/ PUSH P,[=5500] ; THIS IS OK
DPGT&DPGT.-3/ PUSH P,3 ; IT SEEMS TO THINK AC3 CONTAINS A 1
DPGT&DPGT.-2/ PUSHJ P,ARRMAK
This, of course, gets a "UPPER BOUND<LOWER BOUND" error
message, for constant bounds yet! Anyway, the problem
goes away if you put an "IF TRUE THEN" in front of
the BEGIN "DPGT". Is that enough?
22-NOV-72 2341 MA,JAM
Dear Ail,
CASE n OF (ITV, ITV, ... ITV) generates, in at least one case
<case check>
JRST @TABLE(IDX)
PUSH P,ITV
JRST DONE
...
PUSH P,ITV
JRST DONE
TABLE: .-...
.-...
...
TABLE-2
DONE: POP P,TBITS2
MOVE A,0 ;!!!!!!!!!!!
....
This is fairly recent (MOVE s/b MOVE A,TBITS2 or whatever).
DCS
20-NOV-72 0341 SLS,DCS
I RAN INTO PROBLEMS WHEN USING THE SAIL DPB COMMAND.
THE CODE GENERATED FOR THE INSTRUCTION
DPB(A,POINT(11,BUFX[POINTER],10))
SEEMED TO LOAD A INTO REGESTER 10 AND PROMPTLY DEPOSIT REG 11.
THE PROGRAM IS TEST.SAI ON [1,EMC], AND THE OFFENDING LINE IS IN THE
AIVCT1 PROCEDURE FOUND ON PAGE 4, I BELIEVE.
19-NOV-72 0831 1,EMC
HELP!
DON'T PUT UP THE NEW SAIL.
TWO DEMOS ON MONDAY. THIS WOULD
BE THE 4TH DEMO IN SUCCESSION IMMED
AFTER A SAIL CHANGE.
TOB
07-DEC-72 1419 H,HJS
K PINGLE FOUND A BUG HAVING TO DO WITH AN ILLEGIT. ARRAY NAME IN AN
ARERR UUO FOR COMPLICATED EXPRS. SERIOUS ENOUGH TO FIX. SEE BUG #KR.
DCS
06-DEC-72 2219 SLS,DCS
NASTY BUG IN SAIL SETBREAK(TABLE,STRDELIM,STRDELETE,SWITCHES);
IF YOU DO A SETBREAK WITH CHARACTERS TO BE DELETED,
THEN LATER IN THE PROGRAM YOU DO ANOTHER SETBREAK ON THE SAME TABLE NUMBER
WITH NULL STRDELETE, IT CONTINUES TO USE THE OLD STRDELETE!!!!
06-JAN-73 1737 1,REM
Is my observation correct? I have a block full of
CONTINUEs, and I find that the first one jumps to
the second, the second jumps to the third, and so
on to the last one!!???
04-JAN-73 0959 MA,JAM
The SAIL error: BEGIN AND END DO NOT MATCH
could be more helpful in telling which are
the BEGIN block names.
19-DEC-72 1609 WRU,TOB
JAM here. I have a SAIL program that I said ↑C - SAVE
to. The dump copy is SAVBUG.DMP[MA,JAM]. If you RUN it,
it generally says "ERROR IN JOB 26, PC EXCEEDS MEM BOUND
AT USER 400013", indicating to me that the second segment
isn't hooked up. If you GET it and START it, sometimes it
works and sometimes not. This doesn't seem to happen if I
SAVE the program before it is ever run for the first time.
If I start it up, then stop it and save it, this often
happens.
Please delete the file SAVBUG.DMP[MA,JAM] when
you are finished with it.
18-DEC-72 1151 MA,JAM
export version of sail should not have dump never bit on in
rel files created. fancyy technique for writing over ddt doesn't seem
to work with export.
jim low
16-DEC-72 1444 S,JRL
THE 7-LINE PROGRAM BUG.SAI[1,REM] COMPILES INCORRECTLY BY SAIL.
JNAM←CVSIX("[LXGP]"); COMPILES AS MOVSI NIC,0;MOVEM NIC,JNAM;
14-JAN-73 1824 1,REM
YOU OUGHT TO FIX SAIL SO YOU CAN SPECIFY ODD FILE NAMES, LIKE [-AP-].DMP
IN AN ENTER. PERHAPS, ADOPT THE COPY CONVENTION ABOUT ↓ TO SURROUND A
QUOTED NAME.
01-FEB-73 1236 TAP,REG
There is a deeper bug but you can cure your immediate problem by parenthesizing
the expression TK([A⊗O≡V]) in your macro IV. Syntactically the parens are
required since a boolean expression inside a foreach associative context musht
be parenthesized.
jim
06-FEB-73 1126 S,JRL
IT USED TO BE THAT INCHWL WAS ONLY TERMINATED BY <CRLF> NOT
BY <ALT> OR <LF> OR BARE <CR> OR ANY OTHER ACTIVATION CHARACTER.
A FEW MONTHS AGO INCHWL BEGAN TO BE TERMINATED BY THE OTHER ACTIVATION
CHARACTERS AS WELL. THIS LASTED FOR ABOUT A MONTH, THEN RETURNED TO
THE <CRLF> ONLY METHOD. NOW TONITE I FIND THAT INCHWL IS AGAIN TERMINATED
BY ANY ACTIVATION CHARACTERS. WHY DOES IT KEEP CHANGING???
06-FEB-73 0124 1,REM