terryheidelberg
commented
9 years ago [extracting from some email exchanges between Paul and me:]
The "problem" appears if one uses "X" as the first character of the object files generated by the batch deck -- CANDE just whacks off the first character:
FILE~
[now run batch deck that compiles to several X... named object files]
FILE~
XBAS XCOB XTSP XALG XFTN XXAL
#
LIST FILES~
09/07/84 TERRY 07:07 PMNAME TYPE RECS SEGS CREATED ACCESSED W/R W/B S-F LOCKD BY
ALG OBJ(C) 10 10 09/07/84 * 09/07/84 30 30 10
BAS OBJ(A) 12 12 09/07/84 * 09/07/84 30 30 10
COB OBJ(F) 23 23 09/07/84 * 09/07/84 30 30 10
FTN OBJ(T) 13 13 09/07/84 * 09/07/84 30 30 10
TSP OBJ(X) 13 13 09/07/84 * 09/07/84 30 30 10
XAL OBJ(U) 10 10 09/07/84 * 09/07/84 30 30 10
6 FILES 81 SEGMENTS 81 RECORDS
END LFILES 1.1 SEC.
So my take is: even though batch decks and CANDE share a file namespace, CANDE assumes(?) that it 'owns' the first character territory of all of the file names. This wouldn't be so bad if the docs spelled this out, but all I remember reading is that CANDE filenames are limited to six chars. So perhaps this is mostly a lack-of-documentation problem.
There very well could be more to this story, however.
apparent errors in object-file types, produced by CANDE command "LIST FILES", which invokes LFILES/CANDE; this appears to be an off-by-one error; I've spent some time looking through code in CANDE and LFILES, but haven't located a problem there yet (but i did discover some features not in the CANDE documentation, however)
Submitted by Terry Heidelberg, 2015-05-04.