Upvoted for constructive critic! :)

First, that's not the final interface, just a prove of concept.

> maybe a (&) prototype might help

That's the plan, but for testing and demonstration I needed a lambda.

> "because that's how it works", ie, enforced cargo-culting.

I don't understand your point here.

There are different use cases at my job already

• we have a lot of legacy code without placeholders.
• colleagues are reluctant to adjust it
• some colleagues insist they need "named" placeholders
• I need a lot of boiler plate to prepare (?,?,...) lists

Legacy code looks like

local $"=",";
my $sth = $dbh->prepare(
       "SELECT * FROM $table 
        WHERE lastname  = $lastname 
        AND   firstname IN (@firstnames)
       "
);
$sth->execute( $lastname, @firstnames );
[download]

I want to change it to something like:

my $sth = $dbh->xprepare( ph {
       "SELECT * FROM $_table 
        WHERE lastname  = $lastname 
        AND   firstname IN (@firstnames)
       "
});
$sth->xexecute();
[download]

(not sure yet, but methods can't have prototypes and DBI allows to hook in with callbacks)

> (access the variables outside their scopes, delay the interpolation), so that's magic where the implementation leaks into the calling context, the wrong kind of magic IMHO.

I don't get your point, nothing is leaking here. I'm overwriting the pad with references of new vars. This means all effects are restricted to the code block, which is only executed once.

My goals are:

• DRY-ness : avoiding repetition of code and boilerplates
• more flexibility and speed when SQL changes
• less errors
• better control over code quality

update

While writing this post I had to re-edit the "legacy" part twice, because I mistyped repeated variables.

And it's still wrong. ;-)

---

---

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! —

• How do I compose an effective node title?
• How do I post a question effectively?
• Markup in the Monastery

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:
	&		&
	<		&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.