Trailing-Edge
-
PDP-10 Archives
-
bb-bt99g-bb
-
ftn10.d11
There are 2 other files named ftn10.d11 in the archive. Click here to see a list.
EDIT DESCRIPTIONS FOR FORTRAN-10-V10
EDIT 336 FOR FORDDT
[SYMPTOM]
Auopatch-built FORDDT does not reflect true version number.
[DIAGNOSIS]
Autopatch won't update the version number of a reserved edit number if
it is the only edit for a particular freeze period.
[CURE]
Force a dummy update.
********************************************************************************
EDIT 4211 FOR FOROTS
SYMPTOM
A program which merely OPENs a file numerous times for APPEND will run out
of channels, even though the file is properly CLOSED.
DIAGNOSIS
When FOROTS opens a file for append, it attempts to first create a file,
so that the file is guaranteed to be in the "top-level" area. Since the
FILOP to create the file has the "allocate a channel" bit on, a channel
is allocated and TOPS-10 does not deallocate it.
CURE
FOROTS must deallocate the channel after a failing FILOP. This is
accomplished by edit 4211.
********************************************************************************
EDIT 4212 FOR FOROTS
SYMPTOM
Using FORTRAN-10, when in DIALOG, if a file is specified for RENAME
which already exists, and then the user specifies a different filename
which succeeds, the resultant file has a creation date sometime in 1974.
DIAGNOSIS
When TOPS-10 gets a rename failure, it places the error code in the
right half of .RBEXT in the LOOKUP/ENTER block corresponding to the
filename to which the file was to be renamed, thus destroying the
creation date FOROTS put there.
CURE
After a rename failure, copy the right half of .RBEXT from the original
file's LOOKUP/ENTER block. This is accomplished by edit 4212.
********************************************************************************
EDIT 4213 FOR FOROTS
SYMPTOM
If OPENing a file on magtape with RECORDTYPE='FIXED', if the BLOCKSIZE
specified is not an integral multiple of the RECL specified, an illegally
formatted tape will result, with records spanning block boundaries.
DIAGNOSIS
FOROTS does not attempt to check for this illegal condition.
CURE
Check for the condition, give a fatal error message if found.
********************************************************************************
EDIT 4215 FOR FOROTS
[SYMPTOM]
Underserved "?Bad format bindary file" error reading unformatted
character data.
[DIAGNOSIS]
If the data runs out when reading unformatted character data, FORIO
routine UICZNI improperly clears the flag/value word RECLEN. This
causes a subsequent attempt to read a non-existent LSCW 3 at ILSCWX.
[CURE]
Edit 4215
********************************************************************************
EDIT 2531 FOR FORTRA
[SYMPTOM]
No error message for using an external name (subroutine/function)
in an I/O statement I/O list. Ie;
CALL DAYTIM()
TYPE *,DAYTIM
END
DAYTIM does not get an error message in the TYPE statement's I/O list,
even though it is the name of a subroutine, and is not a variable.
[DIAGNOSIS]
No test is made anywhere to make this warning.
[CURE]
Add a test to output the warning message if a symbol is external
in the output list.
********************************************************************************
EDIT 2532 FOR FORTRA
[SYMPTOM]
Incorrect argument checking "type mismatch" warning message is
given at Link time when passing a subroutine name as an argument.
[DIAGNOSIS]
Compiler is improperly recognizing when a subroutine name is
being passed to a routine. Subroutine names are typeless, but the
compiler is outputting a "type" to Link to do argument checking with.
[CURE]
Do not output any "type" for any external name to Link unless the
name is known to be a function name. The only way that this can be
known is if the external name is called in the program as a function.
********************************************************************************
EDIT 2533 FOR FORTRA
[SYMPTOM]
/FLAG:ANSI produces an erroneous 'commas needed' flagger warning
when quotes appear within an alpha literal in a FORMAT statement.
[DIAGNOSIS]
Routine FORMATSYN in module FORMAT sees quotes within alpha
literals as two literals in a row. The flagger thus complains because
it thinks that there should be a comma separator.
[CURE]
Recognize the case of one alpha literal immediately following
another, and suppress the warning message in that case.
********************************************************************************
EDIT 2534 FOR FORTRA
[SYMPTOM]
Duplicate error messages are generated for some bad substring
assignments. For example, the following program produces multiple
error messages because I cannot be both a character function and a
variable.
SUBROUTINE X(I)
CHARACTER*1 I
IF (I(1).EQ.' ') WRITE (5,*) 'HELLO'
I(1:1)='X'
RETURN
END
[DIAGNOSIS]
The routine which puts out the error message is called twice.
[CURE]
Remove the second call to the routine which puts out the error
message.
********************************************************************************
EDIT 2535 FOR FORTRA
[SYMPTOM]
A protected file can not be included from [1,2].
[DIAGNOSIS]
The privilege bit (PO.PRV) in the FILOP arg block for the
included file is turned off.
[CURE]
Turn on the privilege bit.
********************************************************************************
END OF FORTRAN-10-V10