Enter your search terms Submit search form
	Web pdp-10.trailing-edge.com

                 EDIT DESCRIPTIONS FOR APLSF-10-V2                              
  
  
                             EDIT 531    FOR APLSF
  
  
  
  
[SYMPTOM]
  
If the input line was the last line in the file, and it  did
not  have a CR at the end of the line, a SYNTAX ERROR, VALUE
ERROR, or SYSTEM ERROR results.
  
[DIAGNOSIS]
  
A null codestring gets created, and  the  activation  record
does  not  point to any codestring.  The syntax machine gets
confused somewhere, and generates various errors.
  
[CURE]
  
Instead of making the input look like CR LF ZILGN, append CR
LF ZILGN to the input and continue.  If it is really the end
of file, then the correct  value  (0  75  .RO  0)  is  still
returned.
********************************************************************************
  
  
                             EDIT 533    FOR APLSF
  
  
  
  
[SYMPTOM]
  
A system error can result after  loading  a  workspace  that
just barely fits into memory.
  
[DIAGNOSIS]
  
APLSF needs a small amount of free memory in  any  workspace
to  create  the  next  codestring  to  be  executed.  If the
codestring space isn't available, a system error is  usually
the result.
  
[CURE]
  
Before a new workspace is loaded, make sure that there  will
be  enough  memory  for  the  new  workspace  and  the  next
codestring.   This  means  that  a  workspace   that   could
previously be loaded in 20K may now require 21K.
********************************************************************************
  
  
                             EDIT 534    FOR APLSF
  
  
  
  
S 
  
     The expression  'M"-$"LI9'  $  .NG1  gets  an  "illegal
instruction" trap.
  
D 
  
     The wrong register was  being  used  to  calculate  the
left-justification   caused   by   the  L  qualifier.   This
clobbered the  register  that  held  the  length  of  the  M
qualifier (left decoration on minus).
  
C 
  
     Use the correct register.
********************************************************************************
  
  
                             EDIT 535    FOR APLSF
  
  
  
  
[SYMPTOM]
  
The APL character .LD doesn't work properly in filenames.
  
[DIAGNOSIS]
  
Device names, file names, and extensions were not allowed to
begin with .LD .  The at sign in the filename was translated
into .DD instead of .LD .  On the 20, /DA and /BU files with
at signs gave various errors.
  
[CURE]
  
Allow device names, file names, and extensions to begin with
.LD  .   Make  sure  that  the  at  sign  in the filespec is
translated into .LD .  On the 20, put a control V  in  front
of the at sign in the filename so the monitor won't treat it
as a special character.
********************************************************************************
  
  
                             EDIT 536    FOR APLSF
  
[SYMPTOM]
  
Edit 531 only worked if the last line in the file has one character.
  
[DIAGNOSIS]
  
In QUOTL, CR LF and ZILGN were being put in the text string after  the
first character, effectively truncating it.
  
[CURE]
  
Don't insert CR LF ZILGN into the string at all.  They are already  at
the end of the string.  Just update INPTR properly and continue.
********************************************************************************
  
  
                             EDIT 537    FOR APLSF
  
  
  
  
[SYMPTOM]
  
Blanks disappear from the middle  of  lines  with  edit  511
installed.
  
[DIAGNOSIS]
  
Characters are converted from ninebit to ASCII one at a time
and put in AOBUF.  Characters are output whenever AOBUF gets
full.  When the buffer is output, APL  cannot  tell  if  the
blanks  it  sees at the end of AOBUF are actually at the end
of a line.
  
[CURE]
  
Remove edit 511.  The problem of trailing blanks at the  end
of  the  line  will a restriction until the next development
release.
********************************************************************************
  
  
  
END OF  APLSF-10-V2