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

[ocaml][flightplan] #825

Closed

Conversation

dewagter
Copy link
Member

@dewagter dewagter commented Sep 8, 2014

Error:

<set var="waypoints[WP_START].x" value="...
works fine in a flightplan.xml but not in an included procedure.xml on my machine.

I get:

BUILD Tester, TARGET sim
Parsing error in 'waypoints[WP_START].x', token '.' ?

Solution:
No lexer when variable does not contain ocml functions

@gautierhattenberger
Copy link
Member

I think this is the "correct" way to go, since in the FP generator for non-procedures 'set' instructions the 'var' attribute is not parsed, only the 'value' attribute.
Adding the parsing of a "field in an array of struct" is possible, but it will impact more files. I'll do it if it is really necessary.

@dewagter
Copy link
Member Author

dewagter commented Sep 8, 2014

If I'm not mistaken, this is what happens at the moment in the main
flight_plan.xml, and that is why it works over there.

-Christophe

On Mon, Sep 8, 2014 at 6:42 PM, Gautier Hattenberger <
notifications@github.com> wrote:

I think this is the "correct" way to go, since in the FP generator for
non-procedures 'set' instructions the 'var' attribute is not parsed, only
the 'value' attribute.
Adding the parsing of a "field in an array of struct" is possible, but it
will impact more files. I'll do it if it is really necessary.


Reply to this email directly or view it on GitHub
#825 (comment).

@dewagter dewagter closed this in 1ad7f90 Sep 9, 2014
@gautierhattenberger gautierhattenberger deleted the no_parsing_when_no_ocaml_functions_are_called branch September 9, 2014 14:19
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.

None yet

2 participants