I find putting a dummy statement after the call usually works fine. E.g. function_call(); 1;

sub function_call { print defined wantarray ? (wantarray?"list\n":"scalar\n") : "void\n" } sub calls_it_1 { print "calls_it_1: "; function_call(); # is this void or not? } sub calls_it_2 { print "calls_it_2: "; function_call(); 1; # this is void } calls_it_1(); my $x = calls_it_1(); my @x = calls_it_1(); calls_it_2(); my $y = calls_it_2(); my @y = calls_it_2(); __END__ calls_it_1: void calls_it_1: scalar calls_it_1: list calls_it_2: void calls_it_2: void calls_it_2: void

In reply to Re: How to enforce void context in Reply? by Anonymous Monk
in thread How to enforce void context in Reply? by docdurdee

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":



  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.