-
Notifications
You must be signed in to change notification settings - Fork 340
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
Move all long2short (l2s) tests into a separate test directory? #8431
Comments
Hmm, all tests are in their own directory with that module name. Why making it different for the ``*.-l2s.sh` tests? I prefer to have them where they are. |
The main reason is, these tests work only when |
OK, but probably what we should do is to make the |
I we can close this now, I think. |
I still prefer to move all l2s tests into a separate test directory, since these tests test the codes in |
In fact, even the fact that the longopt is currently in a bunch of separate headers was discussed at the beginning of this work and the idea was to revise that decision at the end. For example I would rather have each of those .h inserted directly inside the corresponding C code. Anyway, I see no advantage in joining all the l2s tests in a single directory as that makes needlessly harder to find a specific test as comparing to finding it in the directory where all other tests of that module reside. |
Makes sense to me. Closing. |
Perfect thanks, then one of these days I'll start the .h integration move but we'll have to take care to leave room for the missing supplements longoptions. |
We have more than 100 l2s tests, which are tests for translating long-form options to short-form options. Currently, these l2s tests are located in the subdirectory for each module.
I think it makes more sense to put all l2s tests into a separate directory (e.g.,
test/l2s
ortest/long2short
) instead.Thoughts?
Ping @joa-quim @rbdavis
The text was updated successfully, but these errors were encountered: