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

Support __EVAL #23

Open
bovine3dom opened this issue Mar 2, 2019 · 1 comment
Open

Support __EVAL #23

bovine3dom opened this issue Mar 2, 2019 · 1 comment
Labels
enhancement New feature or request

Comments

@bovine3dom
Copy link

bovine3dom commented Mar 2, 2019

commy2 claims that you don't want to reimplement SQF and so don't support __EVAL, which sounds reasonable.

Could you throw an error if armake2 encounters such an expression? It currently just suggests quoting it, which is misleading.

Would you be willing to offer an __ARMAKEVAL that used e.g https://github.com/rekka/meval-rs? In our projects we mostly just use it for little bits of maths. baermitumlaut pointed out that one can just remove the __EVAL and ArmA will magically do the maths anyway for my use-case.

@KoffeinFlummi KoffeinFlummi added the enhancement New feature or request label May 13, 2019
@jonpas
Copy link
Collaborator

jonpas commented Jun 20, 2019

This can be resolved by letting Arma evaluate __EVAL expressions on load, that is accomplished by storing the string and marking it as "expression" (value sub-type 4) in binarized config (add here) and in turn editing the parser to read __EVAL correctly and pass required data along.

Simple things should still be evaluated during binarization if possible, to speed up load times (simple math expressions and other things not using SQF).

Source: @dedmen

@jonpas jonpas changed the title Emit error on __EVAL Support __EVAL Jun 20, 2019
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

3 participants