comment on

Hi mhearse,
I'm struggling to make nested code work inside sprintf. Can someone advise?
1. My candy advise, DO NOT BE extremely CLEVER! Simply use your for loop outside the sprintf

2. However, if you want to do want you want to do, because you are using perl, then instead of using a subroutine or an eval, why not use a do{...} like so: not REALLY tested

#!/usr/bin/perl -w
use strict;

my %hash = (
    son    => { year => 2006, name => 'Paul', },
    father => { year => 1981, name => 'Ryan', },
    mother => { year => 1978, name => 'Bose', },

);

print sprintf(
    "%s: %s",
    'Person' . $/,
    do {  ## <== note here
        my $order;
        for ( sort keys %hash ) {
            $order .= join ' | ' => $_, %{ $hash{$_} }, $/;
        }
        $order;
      }
);
[download]

check perldoc -f do
from your CLI to see why this over eval.

3. IMHO, don't be too clever about your program. A simple program often save the day!

UPDATE:
Apparently, while I was still trying to frame my answer to this, BrowserUk came up first! ++!

If you tell me, I'll forget.
If you show me, I'll remember.
if you involve me, I'll understand.
--- Author unknown to me

In reply to Re: sprintf: using nested code by 2teez
in thread sprintf: using nested code by mhearse

Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
Want more info? How to link or How to display code and escape characters are good places to start.


P is for Practical
	PerlMonks