Parse.c DEF_RULE macro - How does it works?

[festfire]

Hello. I am currently working on porting micropython to IAR Workbench environment.
Naturally I encountered numerous errors, though I can't resolve all of them without help. For now I have a trouble understanding how parse.c and grammar.h works - DEF_RULE macro just blows my newbie mind.
The error is "too many initializer values" in https://github.com/micropython/micropyt ... mmar.h#L40 and so on.
CC's preprocessor gives me this:

Code: Select all

static const rule_t rule_single_input = { RULE_single_input, or(3), { tok(NEWLINE), rule(simple_stmt), rule(compound_stmt) } };

IAR doesn't compile that

[dhylands]

Hello. I am currently working on porting micropython to IAR Workbench environment.
Naturally I encountered numerous errors, though I can't resolve all of them without help. For now I have a trouble understanding how parse.c and grammar.h works - DEF_RULE macro just blows my newbie mind.
The error is "too many initializer values" in https://github.com/micropython/micropyt ... mmar.h#L40 and so on.
CC's preprocessor gives me this:

Code: Select all

static const rule_t rule_single_input = { RULE_single_input, or(3), { tok(NEWLINE), rule(simple_stmt), rule(compound_stmt) } };

IAR doesn't compile that

That looks incomplete. The or, tok, and rule macros don't seem to be expanded.

I ran:

Code: Select all

make build-PYBV10/py/parse.pp

and I get the following line for rule_single_input from the build-PYBV10/py/parse.pp file:

Code: Select all

static const rule_t rule_single_input = { RULE_single_input, ((0x10) | 3), { ((0x1000) | MP_TOKEN_NEWLINE), ((0x2000) | RULE_simple_stmt), ((0x2000) | RULE_compound_stmt) } };

[pfalcon]

I ran:

Code: Select all

make build-PYBV10/py/parse.pp

I missed such rule being present, but shouldn't it be build-PYBV10/py/parse.i ?

[dhylands]

I ran:

Code: Select all

make build-PYBV10/py/parse.pp

I missed such rule being present, but shouldn't it be build-PYBV10/py/parse.i ?

It seems many build systems don't bother with it. I find it just useful enough to put it in. The rule is here:
https://github.com/micropython/micropyt ... mk#L48-L50

As to .i versus .pp, I think its really just personal preference. Since I was the one creating the initial mkrules.mk file, my personal preference was to use .pp (short for preprocess), because .i doesn't have any meaning (some intermediate).

make doesn't have any builtin rules for either one.