Skip to content

Conversation

@masinter
Copy link
Member

grep --text -lri \is.no.randaccessp medley
showed there were a number of .LCOM files that seemed to reference this missspelled function.
I can't quite see how that happens. But this PR, which just has the files recompiled.

For each file where it found a hit, I did

LOAD(file PROP)
BCOMPL(FILE)
F

I didn't carefully isolate these from unfortunate declarations (as we saw with
INTERPRESS) because for the most part it's isolated. I also didn't give in to the temptation to obsolete MOD44IO DSKDISPLAY and other obsolete files, although the temptation was strong.

Will fix #1224

Copy link
Contributor

@rmkaplan rmkaplan left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Surprised that GITFNS.LCOM is in the list (I don't see that GITFNS references that). I wonder whether it comes from a macro some where?

But recompiling is presumaby harmless.

@rmkaplan rmkaplan merged commit 2e7b88d into master Nov 21, 2023
@masinter masinter deleted the recompile-all-no-randaccessp branch December 2, 2023 02:38
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

(SETFILEPTR T 0) results in UDF \IS.NO.RANDACCESSP

3 participants