I'm encountering DNUs in the Styler in Pharo 4.0. Is someone else encountering those as well? A way to reproduce: RBParser parseFaultyMethod: 'test ^ ()' Whereas: RBParser parseFaultyMethod: 'test ^ ^ self' correctly returns an AST with RBParseErrorNode(s) inside. Thierry
On 06 Oct 2014, at 14:29, Thierry Goubier <thierry.goubier@gmail.com> wrote:
I'm encountering DNUs in the Styler in Pharo 4.0. Is someone else encountering those as well?
A way to reproduce:
RBParser parseFaultyMethod: 'test ^ ()â
When I execute that I do not get any problems with the styler, but the faulty expression parsing itself fails for this input⦠(dnu #addParenthesis: on the ErrorNode) I get the same error in Pharo3. Marcus
2014-10-06 17:06 GMT+02:00 Marcus Denker <marcus.denker@inria.fr>:
On 06 Oct 2014, at 14:29, Thierry Goubier <thierry.goubier@gmail.com> wrote:
I'm encountering DNUs in the Styler in Pharo 4.0. Is someone else encountering those as well?
A way to reproduce:
RBParser parseFaultyMethod: 'test ^ ()'
When I execute that I do not get any problems with the styler, but the faulty expression parsing itself fails for this input...
(dnu #addParenthesis: on the ErrorNode)
I get the same error in Pharo3.
Marcus
I had the setting on "use AST styler" which explains the DNUs. I turned it
off so that's solved. The sequence above shows that the RBParserErrorNode thing [1] works in some cases and not all. Are you planning something in that area? Thierry [1] encapsulating a syntax error in a RBParserErrorNode so that: styling can happen on a correct part of the code; and that (maybe) parsing can continue.
On 06 Oct 2014, at 17:12, Thierry Goubier <thierry.goubier@gmail.com> wrote:
2014-10-06 17:06 GMT+02:00 Marcus Denker <marcus.denker@inria.fr <mailto:marcus.denker@inria.fr>>:
On 06 Oct 2014, at 14:29, Thierry Goubier <thierry.goubier@gmail.com <mailto:thierry.goubier@gmail.com>> wrote:
I'm encountering DNUs in the Styler in Pharo 4.0. Is someone else encountering those as well?
A way to reproduce:
RBParser parseFaultyMethod: 'test ^ ()â
When I execute that I do not get any problems with the styler, but the faulty expression parsing itself fails for this inputâ¦
(dnu #addParenthesis: on the ErrorNode)
I get the same error in Pharo3.
Marcus
I had the setting on "use AST styler" which explains the DNUs. I turned it off so that's solved.
Yes, this is not completely working yet⦠we need to do the move and fix all the bugsâ¦
The sequence above shows that the RBParserErrorNode thing [1] works in some cases and not all.
Are you planning something in that area?
Planning yes⦠but not started yet⦠I need to finish other things before. So every contribution is welcome...
Thierry
[1] encapsulating a syntax error in a RBParserErrorNode so that: styling can happen on a correct part of the code; and that (maybe) parsing can continue.
Marcus can you open a roadmap file on github so that we know and can take action. This is a nice way to share knowledge and possible actions. Stef
I had the setting on "use AST styler" which explains the DNUs. I turned it off so that's solved.
Yes, this is not completely working yet⦠we need to do the move and fix all the bugsâ¦
The sequence above shows that the RBParserErrorNode thing [1] works in some cases and not all.
Are you planning something in that area?
Planning yes⦠but not started yet⦠I need to finish other things before. So every contribution is welcome...
Thierry
[1] encapsulating a syntax error in a RBParserErrorNode so that: styling can happen on a correct part of the code; and that (maybe) parsing can continue.
On 07 Oct 2014, at 08:02, stepharo <stepharo@free.fr> wrote:
Marcus can you open a roadmap file on github so that we know and can take action. This is a nice way to share knowledge and possible actions.
Ok, I will write something.
Stef
I had the setting on "use AST styler" which explains the DNUs. I turned it off so that's solved.
Yes, this is not completely working yet⦠we need to do the move and fix all the bugsâ¦
The sequence above shows that the RBParserErrorNode thing [1] works in some cases and not all.
Are you planning something in that area?
Planning yes⦠but not started yet⦠I need to finish other things before. So every contribution is welcome...
Thierry
[1] encapsulating a syntax error in a RBParserErrorNode so that: styling can happen on a correct part of the code; and that (maybe) parsing can continue.
participants (3)
-
Marcus Denker -
stepharo -
Thierry Goubier