[Pharo-project] [update 2.0] #20403
20403 ----- Issue 6989: Move DebuggerMethodMap to Compiler package http://code.google.com/p/pharo/issues/detail?id=6989 Issue 6988: Run #cleanUpForRelease in postscript http://code.google.com/p/pharo/issues/detail?id=6988 Issue 6894: Add Error tolerant parsing to RB http://code.google.com/p/pharo/issues/detail?id=6894 Diff information: http://ss3.gemstone.com/ss/Pharo20/Kernel-MarcusDenker.1252.diff http://ss3.gemstone.com/ss/Pharo20/Compiler-MarcusDenker.360.diff http://ss3.gemstone.com/ss/Pharo20/AST-Core-MarcusDenker.103.diff -- Marcus Denker -- http://marcusdenker.de
Marcus, you are in fire!!! Thanks :) On Fri, Nov 16, 2012 at 8:08 PM, Marcus Denker <marcus.denker@inria.fr>wrote:
20403 -----
Issue 6989: Move DebuggerMethodMap to Compiler package http://code.google.com/p/pharo/issues/detail?id=6989
Issue 6988: Run #cleanUpForRelease in postscript http://code.google.com/p/pharo/issues/detail?id=6988
Issue 6894: Add Error tolerant parsing to RB http://code.google.com/p/pharo/issues/detail?id=6894
Diff information: http://ss3.gemstone.com/ss/Pharo20/Kernel-MarcusDenker.1252.diff http://ss3.gemstone.com/ss/Pharo20/Compiler-MarcusDenker.360.diff http://ss3.gemstone.com/ss/Pharo20/AST-Core-MarcusDenker.103.diff
-- Marcus Denker -- http://marcusdenker.de
-- Mariano http://marianopeck.wordpress.com
I really like the idea of the errorNode. Stef On Nov 16, 2012, at 8:08 PM, Marcus Denker wrote:
20403 -----
Issue 6989: Move DebuggerMethodMap to Compiler package http://code.google.com/p/pharo/issues/detail?id=6989
Issue 6988: Run #cleanUpForRelease in postscript http://code.google.com/p/pharo/issues/detail?id=6988
Issue 6894: Add Error tolerant parsing to RB http://code.google.com/p/pharo/issues/detail?id=6894
Diff information: http://ss3.gemstone.com/ss/Pharo20/Kernel-MarcusDenker.1252.diff http://ss3.gemstone.com/ss/Pharo20/Compiler-MarcusDenker.360.diff http://ss3.gemstone.com/ss/Pharo20/AST-Core-MarcusDenker.103.diff
-- Marcus Denker -- http://marcusdenker.de
On Nov 16, 2012, at 7:30 PM, Stéphane Ducasse <stephane.ducasse@inria.fr> wrote:
I really like the idea of the errorNode.
This is needed to replace the ad-hoc parser that is in the syntax highlighting. With the error nodes, we can just use the same parser and implement syntax highlighting as a normal visitor on the standard AST. See http://code.google.com/p/pharo/issues/detail?id=6893 (later we can even replace the RBParser by one implemented in PetitParser) Marcus
Stef
On Nov 16, 2012, at 8:08 PM, Marcus Denker wrote:
20403 -----
Issue 6989: Move DebuggerMethodMap to Compiler package http://code.google.com/p/pharo/issues/detail?id=6989
Issue 6988: Run #cleanUpForRelease in postscript http://code.google.com/p/pharo/issues/detail?id=6988
Issue 6894: Add Error tolerant parsing to RB http://code.google.com/p/pharo/issues/detail?id=6894
Diff information: http://ss3.gemstone.com/ss/Pharo20/Kernel-MarcusDenker.1252.diff http://ss3.gemstone.com/ss/Pharo20/Compiler-MarcusDenker.360.diff http://ss3.gemstone.com/ss/Pharo20/AST-Core-MarcusDenker.103.diff
-- Marcus Denker -- http://marcusdenker.de
-- Marcus Denker -- http://marcusdenker.de
On Nov 16, 2012, at 7:44 PM, Marcus Denker <marcus.denker@inria.fr> wrote:
On Nov 16, 2012, at 7:30 PM, Stéphane Ducasse <stephane.ducasse@inria.fr> wrote:
I really like the idea of the errorNode.
This is needed to replace the ad-hoc parser that is in the syntax highlighting. With the error nodes, we can just use the same parser and implement syntax highlighting as a normal visitor on the standard AST.
See
With the error node, it would even be possible to generate code for faulty methods, raising the syntax error again at runtime ;-) Marcus -- Marcus Denker -- http://marcusdenker.de
On Nov 16, 2012, at 11:44 PM, Marcus Denker wrote:
On Nov 16, 2012, at 7:30 PM, Stéphane Ducasse <stephane.ducasse@inria.fr> wrote:
I really like the idea of the errorNode.
This is needed to replace the ad-hoc parser that is in the syntax highlighting. With the error nodes, we can just use the same parser and implement syntax highlighting as a normal visitor on the standard AST.
Excellent we could try to work on autocompletion of code :) by trying to smartly substituting the errorCodeNode by the smallest closing element :) Stef
On Nov 16, 2012, at 4:08 PM, Marcus Denker <marcus.denker@inria.fr> wrote:
20403 -----
Issue 6989: Move DebuggerMethodMap to Compiler package http://code.google.com/p/pharo/issues/detail?id=6989
Issue 6988: Run #cleanUpForRelease in postscript http://code.google.com/p/pharo/issues/detail?id=6988
This seems to break something... I will redo it witout the #cleanUpForRelease (and another example that shows that everything not tested is broken) Marcus -- Marcus Denker -- http://marcusdenker.de
On Nov 17, 2012, at 11:32 AM, Marcus Denker <marcus.denker@inria.fr> wrote:
On Nov 16, 2012, at 4:08 PM, Marcus Denker <marcus.denker@inria.fr> wrote:
20403 -----
Issue 6989: Move DebuggerMethodMap to Compiler package http://code.google.com/p/pharo/issues/detail?id=6989
Issue 6988: Run #cleanUpForRelease in postscript http://code.google.com/p/pharo/issues/detail?id=6988
This seems to break something...
I will redo it witout the #cleanUpForRelease
(and another example that shows that everything not tested is broken)
Ok, undo done. Marcus -- Marcus Denker -- http://marcusdenker.de
Thanks I'm resting after yet another little crisis. Anyway it was fun to go to bern and hack during the moose dojo. I have built a nice little tool. I'm nearly there. This tool will definitively helps the Moosers and synectiquers to freeze their configuration. Stef
This seems to break something...
I will redo it witout the #cleanUpForRelease
(and another example that shows that everything not tested is broken)
Ok, undo done.
Marcus
-- Marcus Denker -- http://marcusdenker.de
participants (3)
-
Marcus Denker -
Mariano Martinez Peck -
Stéphane Ducasse