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
Original bug ID: 424 Reporter: administrator Status: closed Resolution: fixed Priority: normal Severity: minor Category: -for CamlIDL use https://github.com/xavierleroy/camlidl/issues
Bug description
Full_Name: Dmitry Bely
Version: 3.01, camlidl current cvs
OS: Windows NT 4.0
Submission from: d032.p3.col.ru (195.210.132.32)
In case of syntax error Camlidl sometimes points at the wrong
place (sometimes far away from the real place if .idl file is big
enough). Here is an example:
That's a general problem with Yacc parsers: they can shift quite a lot
of text before getting stuck and reporting an error. So, I haven't
addressed this issue.
I still believe the bug is in your code. Here is the more expressive example:
/* line 22 / abracadabra / File wrongnum.idl, line 11, column 1: syntax error
*/
[---cut---]
I don't see how extra parser shifts can cause that ... If yacc detects error too
late, reported line should be greater than the real one (obviously not the case
here). Note also column number, that is far from reality.
The text was updated successfully, but these errors were encountered:
/* line 22 / abracadabra / File wrongnum.idl, line 11, column 1: syntax error
*/
[---cut---]
I don't see how extra parser shifts can cause that ...
Granted. There was indeed something wrong in camlidl: it used to read
its input in "text" mode, not "binary" mode, causing character
positions to be mis-computed. Now, the line reported is correct,
however the column is still wrong because it refers to the file after
preprocessing, which is something like
(22 blank lines)
abracadabra
However, camlidl -nocpp gives the correct location.
Original bug ID: 424
Reporter: administrator
Status: closed
Resolution: fixed
Priority: normal
Severity: minor
Category: -for CamlIDL use https://github.com/xavierleroy/camlidl/issues
Bug description
Full_Name: Dmitry Bely
Version: 3.01, camlidl current cvs
OS: Windows NT 4.0
Submission from: d032.p3.col.ru (195.210.132.32)
from #2773:
I still believe the bug is in your code. Here is the more expressive example:
[---cut---]
//
//
//
//
//
//
//
//
//
//
//
//
//
//
//
//
//
//
//
// (20 times)
/* line 22 / abracadabra / File wrongnum.idl, line 11, column 1: syntax error
*/
[---cut---]
I don't see how extra parser shifts can cause that ... If yacc detects error too
late, reported line should be greater than the real one (obviously not the case
here). Note also column number, that is far from reality.
The text was updated successfully, but these errors were encountered: