You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When the conversion name for a dataitem has square-brackets in the middle of it, the parser seems to assume that that's the end of the name.
When I read the conversion of a dataitem like this, it only includes everything up to the closing square-bracket.
Snippets:
From the A2L file: /begin MEASUREMENT ***.******_12 "" UWORD ***.******[12]_******* 0 0.0 0.0 65535.0 ECU_ADDRESS 0x******** DISPLAY_IDENTIFIER ***.******[12] /end MEASUREMENT
An error message from when the parser was running (after calling db.import_a2l(...)) **************.a2l::line ****:** extraneous input '_*******' expecting {INT, HEX}
The text was updated successfully, but these errors were encountered:
A completely new parser written in C++ is on the way, which fixes this and other parsing related problems (not to mention the performance boost...).
There's some final touch required, but I think it should be ready within the next two weeks.
When the conversion name for a dataitem has square-brackets in the middle of it, the parser seems to assume that that's the end of the name.
When I read the conversion of a dataitem like this, it only includes everything up to the closing square-bracket.
Snippets:
From the A2L file:
/begin MEASUREMENT ***.******_12 "" UWORD ***.******[12]_******* 0 0.0 0.0 65535.0 ECU_ADDRESS 0x******** DISPLAY_IDENTIFIER ***.******[12] /end MEASUREMENT
An error message from when the parser was running (after calling db.import_a2l(...))
**************.a2l::line ****:** extraneous input '_*******' expecting {INT, HEX}
The text was updated successfully, but these errors were encountered: