Berndl, Klaus wrote:
> I have checked in new c.bnf with some new parsing features and some
> fixes (see below), a newly generated semantic-c.el and also a new
> tests/test.cpp which tests latest fixes.
> wchar_t and string-sequences like "str" "str" now works.
Just tested this part and I can comfirm it works now.
>> You have added many additional capabilities to the parser now.
>> Are you getting the correct types of output in ECB? Occasionally
>> in the past I've added support for a stray & or const in type
>> definitions for variables. Later, when one of the token->text
>> functions are called, it shows up in the wrong place. For C this
>> has been one of the more challenging aspects of translating C
>> into a token, then back out again. When last I ran tests, it was
>> pretty good, but missing the finer points of * and & placement.
>> With all your new template and const work it would be good to
>> asses the situation.
> Done! You were right, Eric, in the function-arguments correct
> pointer counting and const recognizing was disrupted after my
> latest changes. This means parsing was ok, but the output was
> Now i have fixed all this and now it works again! Now all the
> output from the new parsing capabilities is correct - at least for
> this i have tested ;-)
Hmm, are references important too? Just asking, because references are
not recognised but simply ignored, I think.