On Thu, Aug 2, 2012 at 1:01 PM, Giorgio Valoti <giorgi...@me.com> wrote:
> Hi,
> I’m testing a macro expansion with =expands-to=>. The macro being tested
> uses gensym, though.
> Is there a way to ignore the generated symbols within =expands-to=> ?
> I'd recommend you just test the result of *using* the macro instead.
+1.
I have a project that uses macros fairly heavily. It in fact has macros that call functions that write macros. Some of the tests are fairly decently documented for a package that no one uses, and they might serve as examples.
Il giorno 03/ago/2012, alle ore 17:11, Brian Marick ha scritto:
> On Aug 3, 2012, at 3:14 AM, Alex Baranosky wrote:
>> I'd recommend you just test the result of *using* the macro instead.
> +1.
> I have a project that uses macros fairly heavily. It in fact has macros that call functions that write macros. Some of the tests are fairly decently documented for a package that no one uses, and they might serve as examples.
Il giorno 03/ago/2012, alle ore 17:11, Brian Marick ha scritto:
> On Aug 3, 2012, at 3:14 AM, Alex Baranosky wrote:
>> I'd recommend you just test the result of *using* the macro instead.
> +1.
> I have a project that uses macros fairly heavily. It in fact has macros that call functions that write macros. Some of the tests are fairly decently documented for a package that no one uses, and they might serve as examples.
> This package seems very useful and I was wondering what is the relation with Midje, if any. Do you have any plans to fold Peano back into Midje?
I wrote this up as a proof of concept and to give me a better (more compelling) example of logic programming to use in my Software Craftsmanship North America talk.
I think Peano is a good idea -- I sure wish I'd had it on the last two Rails projects I've been working on -- but it won't go any further until and unless I get some Clojure work that needs something like it.
I'd be reluctant to put it in Midje core mainly because it doesn't work "out of the box". In order to use it on your own data, you have to write "selector and generator" code that isn't trivial.
-----
Brian Marick, Artisanal Labrador
Contract programming in Ruby and Clojure
Occasional consulting on Agile