Not totally from what I saw and monday all the tests were green and we published the code because it was the end ofOn Oct 11, 2013, at 9:47 PM, Denis Kudriashov <dionisiydk@gmail.com> wrote:As Markus said it is good idea to add #argumentNames to block.�What exactly you want to see at TxText?I ask because Igor make big progress on his design implementation which I think will replace my work totally.So if you want to join his development you don't need my code at all (remove it)a large refactoring to get immutable objects into place and having tests were cool.When we start a new behavior like copyText we started with tests.StefBut my version (which is at configuration) is usable and works nice for end user applications. I actually use it for my tasks.�2013/10/11 Camillo Bruni <camillobruni@gmail.com>
I recently checked the progress on TxText and I saw that half of the tests fail
under 3.0 due to an incompatibility in Mocketry on BlockClosure>>#argumentNames
trying to decompile the block contents. This feature is no longer available,
instead you have to access the AST directly:
BlockClosure >> #argumentNames
� � � � ^ self sourceNode arguments collect: [ :each | each name ]
Would it be possible to integrate that on a 3.0 branch? It's quite a pity to
waste so many tests :)