Re^3: Best practices for warnings about wrong context

It does not. The body expects a string/scalar. $c->response->body(defined wantarray); prints "1". Maybe I am missing the point because a setter like ->body expects a value and is therefore never going to be a void context call; it's a strange question / concept to want to demonstrate.

Comment on Re^3: Best practices for warnings about wrong context Select or Download Code

Replies are listed 'Best First'.
Re^4: Best practices for warnings about wrong context by vsespb (Chaplain) on Oct 05, 2015 at 16:55 UTC
In this example wantarray returns context in which the action called, not related to what body expects, so `$c->response->body(wantarray)` [download] same as `my $x = wantarray; $c->response->body($x)` [download]	[reply] [d/l] [select]
Re^5: Best practices for warnings about wrong context by Your Mother (Archbishop) on Oct 05, 2015 at 17:23 UTC
Sorry, you are quite right about that. I was talking crazy. It still does not print "1" though, as you're right, same `wantarray` context so nothing could be different, but returns false but defined.	[reply] [d/l]
Re^6: Best practices for warnings about wrong context by vsespb (Chaplain) on Oct 05, 2015 at 17:33 UTC
hm, in my case it prints "1", and wantarray+1 prints "2". strange. maybe different Catalyst version/plugins/setup. Anyway, defined but false, does not change whole topic idea.	[reply]
Re^7: Best practices for warnings about wrong context by Your Mother (Archbishop) on Oct 05, 2015 at 19:13 UTC