Richard (>>):
>> What am I doing wrong?
Passing constant strings into the macro, instead of code.
r: macro m($code) { quasi { {{{$code}}} } }; class A { m(has
$.x is rw) }; say A.new(:x('OH HAI')).x
rakudo-parrot e32249, rakudo-jvm e32249: OUTPUT«OH HAI»
* masak replies to the p6u email
So, i
Whoops, just noticed this was sent to only me:
I can duplicate your issue, in that the macro is hit, the debug code is
quasi'd, but the resulting class doesn't seem to have a $.b.
Hitting the list to get more discussion on the right way to approach this
particular problem.
On Tue, Dec 17, 2013 a
I would start with
http://strangelyconsistent.org/blog/macros-what-are-they-really for a way
to parse but not execute potentially expensive debug code.
On Sun, Dec 15, 2013 at 10:49 PM, Richard Hainsworth wrote:
> What should be the perl6 idiom for handling debug code?
>
> I am writing a prog
What should be the perl6 idiom for handling debug code?
I am writing a program that will be run with large values and take some
time when it is clear that it is running correctly.
In order to ensure that the program is correct, I have added code to
generate and output intermediate results. I
