RB AST node positions off by one or more characters with Opal ?
Hi all, has anybody noticed that, when getting node positions from a RB parse of the AST, they seem to be off by one character or more? It happens in smart suggestions type of commands for me, but it seems to also happens when the compiler tries to remove unused temporaries and garbles up the temp declaration line? (In the latest 3.0, of course :)) Thierry -- Thierry Goubier CEA list Laboratoire des Fondations des Systèmes Temps Réel Embarqués 91191 Gif sur Yvette Cedex France Phone/Fax: +33 (0) 1 69 08 32 92 / 83 95
On 25 Oct 2013 at 11:16:35, Goubier Thierry (thierry.goubier@cea.fr) wrote:
Hi all,
has anybody noticed that, when getting node positions from a RB parse of the AST, they seem to be off by one character or more? It happens in smart suggestions type of commands for me, but it seems to also happens when the compiler tries to remove unused temporaries and garbles up the temp declaration line?
That one i have seen, yes. I will put it on the list of things to look at soon(ish)
(In the latest 3.0, of course :))
participants (2)
-
Goubier Thierry -
Marcus Denker