acme (email not shown publicly)
http://www.astray.com/
Leon Brocard (aka acme) is an orange-loving Perl eurohacker with many varied contributions to the Perl community, including the GraphViz module on the CPAN. YAPC::Europe was all his fault. He is still looking for a Perl Monger group he can start which begins with the letter 'D'.
Just right (Score:2)
}) %]"> enables the reader to extract information that the single-delimiter style ))))) cannot provide. I think that ))))) is prettier, but less practical.
} is the end of a hash
) is probably the end of a function call
%] is the end of a TT directive
" is the end of text; the following > tells us it's an SGML-ish attribute value
> is the end of an SGML-ish tag
Re: (Score:1)
Funny you say that, ‘cause I was just thinking the same about sigils today. Yeah sure, they’re noisy and can gunk up the code – also, they’re extra red tape that needs to be typed over and over. But they make it so much easier to scan the code! Consider something like this:
You can immediately tell apart the “slots” where variable values go, the static pieces, and the funct
Re: (Score:2)
Re: (Score:2)
I happen to think convenience is pretty.
J. David works really hard, has a passion for writing good software, and knows many of the world's best Perl programmers
Maybe just right with a possible tweak (Score:1)
It may be just right. Mainly because not having so many delimiters could be worse: requiring the need for hard-to-read escaping.
On another note, maybe one of the delimiters of the mentioned template piece could disappear, by writing something like:
where the
qqfilter would add the leading and trailing quotes and would take care of any necessary entity-escaping. It hardly contributes to the original inteMore ways to do it (Score:1)
There's more than five ways to do it :)
As an aside (Score:1)
<a [% href(...) %]>Lorem ipsum</a>
when I look at the stack... (Score:1)
Quoting specifically, not just delimiting (Score:1)
But quoting in particular is more interesting than delimiting in general. Hofstadter wrote a great book about it. Maybe you've heard of it. :)
Using different quoting syntax for different contexts makes perfect sense to me. Here's what your example would have looked like in a fake-lisp syntax I'm making up right now: