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

IE-0030: Extension examples and testing #30

Merged
merged 1 commit into from
Aug 9, 2023
Merged

Conversation

zedlopez
Copy link
Collaborator

@zedlopez zedlopez commented Aug 9, 2023

Proposal: IE-0030
Authors: Graham Nelson
Language feature name: --
Status: Draft
Related proposals: IE-0028, IE-0001
Implementation: None as yet

@zedlopez zedlopez merged commit 614132c into ganelson:main Aug 9, 2023
@curiousdannii curiousdannii added the formal-proposal A formal proposal that has been accepted for consideration by the core Inform team label Oct 29, 2023
@zedlopez
Copy link
Collaborator Author

This would be a really nice, I'm guessing very easy tweak...

For the I7 test source files, instead of:

Test: testname
For: compilation-target

make it...

[ Test: testname ]
[ For: compilation-target ]

and then they can be compiled without any need to trim the header.

@zedlopez
Copy link
Collaborator Author

When one specifies multiple -show flags at once, do they apply to the same compilation sequence, or does it start over fresh with each one? The former would be a nice time-saver if it's not already the case.

It'd also be nice if the Inform6 compilation didn't use -x.

intest is rejecting -internal.

../intest/Tangled/intest -internal inform7/Internal ~/mine/extensions/AW\ Freyr/Hybrid\ Choices-v7_1.i7xd/ -test all
intest: fatal error: no such test case as /home/zed/mine/extensions/AW Freyr/Hybrid Choices-v7_1.i7xd/

I think it's important for extension testing that intest be able to take a -nest parameter, what with extensions commonly having dependencies on other extensions.

@ganelson
Copy link
Owner

I agree about removing -x, and have done that.

I don't think intest should literally support -internal because it isn't tied to Inform in quite so close a way as that. The main.delia testing script does support changing the internal nest with the $$internal variable, which can be set on the command line. Still, that's all rather clunky.

One of my intentions for the next release cycle of Inform is to write a "driver", that is, a better and more consistent command-line interface for the Inform toolchain, using subcommands like "inform build X" and "inform test X" to drive the other tools - this seems now to be considered good CLI practice, and would clarify the currently rather difficult to understand overlapping sets of options on the tools.

@ganelson
Copy link
Owner

On the test file headers, I think that would be an excellent suggestion if we only had test files, but we also have example files, and I want the two to be consistent with each other. That is, I think a test file should model itself more on an example file than on an I7 source file as such.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
formal-proposal A formal proposal that has been accepted for consideration by the core Inform team
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants