Mon, 16 May 2011 14:19:20 +0200fixed build error with gcc 4.5.2
Edouard Tisserant [Mon, 16 May 2011 14:19:20 +0200] rev 294
fixed build error with gcc 4.5.2

Mon, 16 May 2011 12:36:21 +0200Merged with Edouard's modifications
laurent [Mon, 16 May 2011 12:36:21 +0200] rev 293
Merged with Edouard's modifications

Mon, 16 May 2011 11:57:41 +0200Fix bug when debugging located variables of type memory (%M)
laurent [Mon, 16 May 2011 11:57:41 +0200] rev 292
Fix bug when debugging located variables of type memory (%M)

Thu, 21 Apr 2011 11:22:13 +0200Removed dead code
Edouard Tisserant [Thu, 21 Apr 2011 11:22:13 +0200] rev 291
Removed dead code

Thu, 14 Apr 2011 19:17:20 +0100Fixing implementation of CU, CD, and CUD in standard library.
Mario de Sousa <msousa@fe.up.pt> [Thu, 14 Apr 2011 19:17:20 +0100] rev 290
Fixing implementation of CU, CD, and CUD in standard library.

Thu, 14 Apr 2011 19:02:35 +0100Deleting dead code.
Mario de Sousa <msousa@fe.up.pt> [Thu, 14 Apr 2011 19:02:35 +0100] rev 289
Deleting dead code.

Thu, 14 Apr 2011 18:55:31 +0100Merging changes.
Mario de Sousa <msousa@fe.up.pt> [Thu, 14 Apr 2011 18:55:31 +0100] rev 288
Merging changes.

Thu, 14 Apr 2011 18:12:59 +0100Added tracking of order by which tokens are processed by lexical analyser.
Mario de Sousa <msousa@fe.up.pt> [Thu, 14 Apr 2011 18:12:59 +0100] rev 287
Added tracking of order by which tokens are processed by lexical analyser.
This helps in correctly formating error messages when constructs begin in one file, and end in another.

Thu, 14 Apr 2011 17:35:25 +0100Adding tracking of filename in which token is located.
Mario de Sousa <msousa@fe.up.pt> [Thu, 14 Apr 2011 17:35:25 +0100] rev 286
Adding tracking of filename in which token is located.

Thu, 07 Apr 2011 11:40:03 +0200Reverted semantic error message so that Beremiz can parse them and that user can double-click on error message to open related POU and select the faulty line.
Edouard Tisserant [Thu, 07 Apr 2011 11:40:03 +0200] rev 285
Reverted semantic error message so that Beremiz can parse them and that user can double-click on error message to open related POU and select the faulty line.