Re: Digest for spockframework@googlegroups.com - 1 Message in 1 Topic

[Olivier Nguyen]

It would be very nice if someone can post a serie of blog posts on the architecture of Spock so that many of us can look into an advanced topic in a guided way. 

Many of us at work use Spock but none of us understand the internals. 

Sent from my iPhone

On Apr 22, 2013, at 8:14 PM, spockfr...@googlegroups.com wrote:

  Today's Topic Summary

Group: http://groups.google.com/group/spockframework/topics

• Spock's architecture [1 Update]

 Spock's architecture

Luke Daley <lda...@gmail.com> Apr 22 10:20AM +0100  


> Hello everybody,
 
> As some of you may have seen, I will be doing a presentation on the Spock framework. A couple of the things I will be talking about is the overview as well as some of the features of the Spock architecture. I already have what Spock is as a framework overall but I'm not exactly sure what some of the unique features are to the Spock architecture.
 
That's a complicated question, that requires detailed answers.
 
The most notable aspect would have to be without a doubt Spock's use of compile time transformation to achieve its DSL. This is complex stuff though and worthy of its own series of talks just on this. I'd suggest just presenting more generic information on Groovy's compile time transform ability and then extrapolating to Spock's use of it.
 


 

You received this message because you are subscribed to the Google Group spockframework.
You can post via email.
To unsubscribe from this group, send an empty message.
For more options, visit this group.

--
You received this message because you are subscribed to the Google Groups "Spock Framework - User" group.
To unsubscribe from this group and stop receiving emails from it, send an email to spockframewor...@googlegroups.com.
To post to this group, send email to spockfr...@googlegroups.com.
Visit this group at http://groups.google.com/group/spockframework?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

[Luke Daley]

On 23/04/2013, at 4:35 AM, Olivier Nguyen <olivi...@gmail.com> wrote:

> It would be very nice if someone can post a serie of blog posts on the architecture of Spock so that many of us can look into an advanced topic in a guided way.
>
> Many of us at work use Spock but none of us understand the internals.

You have to ask yourself though, would you rather have new & improved Spock features with Peter's time or the blog posts you mention above?

I'd suggest that if you're interested in this then start studying the source code and ask specific questions on things that aren't clear. That would be a more efficient use of Peter's time.

One of the problems with investing time in extensively documenting the internals is that they change so the payoff is not that great.