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
Follow-up to #199 which implemented a really hacky fix that in turn broke some old logic for detecting erroneous C files. See discussion there.
Doing complete macro expansion seems prohibitively difficult (and is one of the biggest stumbling blocks I encountered in starting the parsec project), and xgettext itself doesn't seem to do so.
Maybe it's time to give up the 👻 of writing a half-assed targeted C parser & just let xgettext do the work, then build the calls ex-post? How would one even build a call in the cases causing this issue though?
The text was updated successfully, but these errors were encountered:
Follow-up to #199 which implemented a really hacky fix that in turn broke some old logic for detecting erroneous C files. See discussion there.
Doing complete macro expansion seems prohibitively difficult (and is one of the biggest stumbling blocks I encountered in starting the
parsec
project), andxgettext
itself doesn't seem to do so.Maybe it's time to give up the 👻 of writing a half-assed targeted C parser & just let
xgettext
do the work, then build the calls ex-post? How would one even build a call in the cases causing this issue though?The text was updated successfully, but these errors were encountered: