Re: Contextual::Return blocks: can they be made to return the actual result?

in reply to Contextual::Return blocks: can they be made to return the actual result?

If you have code that uses ref to check the input parameters, you won't have luck using Contextual::Return. The easy approach would be to remove the ref checks in the receiving code.

Out of curiosity, what does Contextual::Return provide to you that "normal" Perl code does not? Do you reallly make so much use of overloaded stringification that using overload is too much hassle?

Personally, I find most of DCONWAYs modules very interesting but of little practical use.

Comment on Re: Contextual::Return blocks: can they be made to return the actual result? Download Code

Replies are listed 'Best First'.
Re^2: Contextual::Return blocks: can they be made to return the actual result? by wanna_code_perl (Friar) on Jul 13, 2013 at 15:27 UTC
Out of curiosity, what does Contextual::Return provide to you that "normal" Perl code does not? Do you reallly make so much use of overloaded stringification that using overload is too much hassle? `wantarray` and `caller` have worked for almost everything I've ever needed, and I need them rarely, at that. In the current case, I was partly exploring C::R's capabilities, to enforce stricter usage of some subs--beyond the typical croak on void context. Truthfully, even if it would have worked flawlessly, I likely would have ended up removing the module dependency once the bulk of development was done and I had unit tests that took over.	[reply] [d/l] [select]

Replies are listed 'Best First'.

Re^2: Contextual::Return blocks: can they be made to return the actual result?
by wanna_code_perl (Friar) on Jul 13, 2013 at 15:27 UTC

Out of curiosity, what does Contextual::Return provide to you that "normal" Perl code does not? Do you reallly make so much use of overloaded stringification that using overload is too much hassle?

wantarray and caller have worked for almost everything I've ever needed, and I need them rarely, at that. In the current case, I was partly exploring C::R's capabilities, to enforce stricter usage of some subs--beyond the typical croak on void context.

Truthfully, even if it would have worked flawlessly, I likely would have ended up removing the module dependency once the bulk of development was done and I had unit tests that took over.

[reply]
[d/l]
[select]

In Section Seekers of Perl Wisdom