I don't think linking to external resources like this is a good idea. We
don't own the end link, it can be dead very easily, especially in the
future. I would rather improve the documentation.
2016-02-24 17:25 GMT+01:00 pledbrook :
> GitHub user pledbrook opened a pull request:
>
> https://gi
If there are no further comments in this thread I will do this as
separate project for now. It can still be included later on
bye Jochen
Ah, good to know.
While merging in the master changes since the antlr4 fork, I noticed that Spock
was indeed in use already, so I haven’t ditched it — yet. For now, it’s only
used for simple things like where-blocks, which can be done only slightly more
clumsily with JUnit.
-Jesper
> On 24. f
It is a show stopper for groovy-core. We must *not* introduce a dependency
on Spock, because it would conflict with the version of Groovy that we are
using, and apply global xforms on Groovy core. While it might be ok, we
want to minimize the risks.
2016-02-24 12:35 GMT+01:00 Paul King :
> Spock
Spock for testing is by no means a show stopper!
On Wed, Feb 24, 2016 at 6:46 PM, Jesper Steen Møller
wrote:
>
> On 24. feb. 2016, at 01.21, Guillaume Laforge wrote:
>
> Sounds cool, Jesper, great to hear about your progress on the Antlr4
> grammar!
> Is there a way we can help you? How can we t
> On 24. feb. 2016, at 01.21, Guillaume Laforge wrote:
>
> Sounds cool, Jesper, great to hear about your progress on the Antlr4 grammar!
> Is there a way we can help you? How can we test drive this? Is the build
> working?
The build works in that the antlr4 branch can be build and tested with
