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

Implement Preprocessor #165

Open
Krzmbrzl opened this issue Jun 3, 2018 · 5 comments
Open

Implement Preprocessor #165

Krzmbrzl opened this issue Jun 3, 2018 · 5 comments
Labels
feature Issues concerning feature-requests
Milestone

Comments

@Krzmbrzl
Copy link
Owner

Krzmbrzl commented Jun 3, 2018

When preprocessing files before parsing them errors like the second one in #162 could be avoided.

But before this can be done, #72 has to be implemented

@Krzmbrzl Krzmbrzl added the feature Issues concerning feature-requests label Jun 3, 2018
@Krzmbrzl Krzmbrzl added this to the ToDo-list milestone Jun 3, 2018
@Krzmbrzl
Copy link
Owner Author

Krzmbrzl commented Jun 4, 2018

This might be helpful: https://github.com/shevek/jcpp

@Krzmbrzl
Copy link
Owner Author

Krzmbrzl commented Sep 7, 2018

The preprocessor should be make use of #72 in order to fix #117

@Krzmbrzl
Copy link
Owner Author

After having implemented the preprocessor it should be used to preprocess config.cpp-files before they get handled inside ModUtils.getFunctions(File, Collection<Function>)

@Krzmbrzl
Copy link
Owner Author

Krzmbrzl commented Oct 2, 2018

Okay as it turns out Arma doesn't use the C-preprocessor... So I'll have to write it from scratch

@Krzmbrzl
Copy link
Owner Author

Krzmbrzl commented Oct 2, 2018

Here's what it need to be able to do: https://community.bistudio.com/wiki/PreProcessor_Commands

Plus Macros inside single quotes are being expanded while the ones inside double quotes are not

- delimits words

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature Issues concerning feature-requests
Projects
None yet
Development

No branches or pull requests

1 participant