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

Switch to MIT license #20

Merged
merged 33 commits into from
Nov 30, 2018
Merged

Conversation

TheCount
Copy link

@TheCount TheCount commented Nov 10, 2018

This PR depends on PR #19.

It has only one additional commit, switching out the GPL boilerplate with the MIT license boilerplate, adding it where it is missing.

It also changes the date range from 1997-2015 to 1997-2018.

This implements #18 (comment).

Remove everything that is either not used at all or guaranteed by C90
anyway.
Tickers are used for testing/benchmarking only, so they can go into a
separate directory.
Break up compare_parsers.tst.in into separate test directory
Break up yaep.tst.in into individual files and create individual tests.
Break up yaep++.tst.in into individual files and create individual
tests.
Deduplicate standard yaep_parse_grammar() type tests.
Deduplicate standard yaep_read_grammar() type tests.
Deduplicate most more complex mains.
Perform analogous deduplications as in
52a15f0,
b931e20,
8e37c71,
a649673,
99e6bb4, and
37d7b4a.
Avoid out-of-bounds access of symb_code_trans_vect when an unknown
terminal appears in the input (see test19).
Also update year range to 1997-2018.

Implements vnmakarov#18.
@vnmakarov
Copy link
Owner

Thank you for trying to improve YAEP and removing the old code (it is dated when people used RCS :).

My biggest concern with your changes is that you are trying to switch YAEP from autoconf to cmake.

They both have advantages and disadvantages. I really would like to save autoconf. First I tried to apply changes without cmake but I found it is too big work. Now I am thinking to save autoconf and cmake so it could be built by any of these tools.

So I am going to work on this. Your pull request is not forgotten but the changes will be applied in a week or two.

@TheCount
Copy link
Author

Yes, I've seen projects using both CMake and autotools (as in configure.ac and Makefile.am), leaving the choice of which one to use to the user.

This works well, but I'd advise to start from scratch with the autotools. Those .tst.in files were a nightmare to maintain (unless they are autogenerated), and the cocom-config.h didn't do anything (it had some useful tests for ANSI-C features, but these days, ANSI-C is a given; no need to test for it).

@vnmakarov vnmakarov merged commit ed64360 into vnmakarov:master Nov 30, 2018
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.

2 participants