Markers do not show up if the problem appear at the end of the alloy file

SpriMoon / alloy4eclipse

Automatically exported from code.google.com/p/alloy4eclipse

0 stars 0 forks source link

Markers do not show up if the problem appear at the end of the alloy file #7

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago

If Alloy4 reports an error in line 22 while the file has only 21 lines
(it happens if there is an error in line 22), then the marker will not show
up in Eclipse Editor.

However, the marker will appear in Eclipse problems view.

Not sure if this should be considered as an upstream Alloy4 problem or
something that we should manage.

Original issue reported on code.google.com by daniel.l...@gmail.com on 27 Mar 2007 at 7:44

GoogleCodeExporter commented 9 years ago

Original comment by daniel.l...@gmail.com on 11 Apr 2007 at 6:37

Added labels: Milestone-M1

GoogleCodeExporter commented 9 years ago

Original comment by daniel.l...@gmail.com on 11 Apr 2007 at 6:38

Added labels: Milestone-M2
Removed labels: Milestone-M1

GoogleCodeExporter commented 9 years ago

Can it have something to do with the CR/LF vs. CR differences?

Where do the character / line conversions come from? Alloy4? Eclipse jface?
Alloy4Eclipse? Do these conversions take into account platform-specific 
character
encoding differences -- i.e., windows vs. the rest of the computing universe?

Original comment by nicolas....@gmail.com on 5 Nov 2007 at 9:57

GoogleCodeExporter commented 9 years ago

No, I think that the problem is related to the way to compiler is detecting 
there is
something wrong: it expects something that is not coming. 
It says it is in line 22 (while there is only 21 lines) because the expected 
code was
fine during the first 21 lines. In line 22, the code was supposed to be there, 
but
was not.

I do not think we can do much about this...

Original comment by daniel.l...@gmail.com on 5 Nov 2007 at 10:16

GoogleCodeExporter commented 9 years ago

Original comment by daniel.l...@gmail.com on 24 Jan 2008 at 9:24

Added labels: Milestone-M4
Removed labels: Milestone-M2

GoogleCodeExporter commented 9 years ago

We really need a fix for this. It has been around for quite a long time.

Original comment by rdrue...@gmail.com on 27 Mar 2008 at 9:55

Added labels: Milestone-M3
Removed labels: Milestone-M4

GoogleCodeExporter commented 9 years ago

I can no longer reproduce the problem. I guess it has been fixed when Felix 
changed
the pos.y for code folding.

Good news: one issue solved for free :)

Original comment by daniel.l...@gmail.com on 2 Apr 2008 at 7:45

Changed state: Fixed