Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

flag filenames in RUN and CALL that do not resolve when loading from String literals #173

Open
StephanWald opened this issue Oct 27, 2024 · 0 comments
Labels
enhancement New feature or request

Comments

@StephanWald
Copy link
Member

StephanWald commented Oct 27, 2024

File names in CALL and RUN are passed as strings. When they are in the source code as String literals RUN "myprog.bbj" and myprog.bbj cannot be resolved in the PREFIX, flag the filename as warning (not error). Do not flag if the String is built dynamically from variables (note: BBUtils.bbj exists in the PREFIX in the BBj install.)

use ::BBUtils.bbj::BBUtils

REM this file does not exist:
use ::BBUtils_xx.bbj::BBUtils_xx

REM these lines would be okay, they will work at runtime
RUN "BBUtils.bbj"
CALL "BBUtils.bbj"

REM these file names do not exist in the project. Should be flagged as as warning (NOT hard error)
RUN "BBUtils_xx.bbj"
CALL "BBUtils_xx.bbj"

REM to be considered: these Strings that resolve to file paths can be dynamic. This should never be flagged:
A$="BBUtils.bbj"
RUN "./"+A$
CALL "./"+A$
@StephanWald StephanWald changed the title flag filenames in RUN and CALL that doe not resolve when loading from String literals flag filenames in RUN and CALL that do not resolve when loading from String literals Nov 2, 2024
@StephanWald StephanWald added the enhancement New feature or request label Nov 2, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant