[Templates] Converting from old template language which allows nested tags into TT template

Fri, 20 Oct 2006 13:37:37 -0400

This is a multi-part message in MIME format.

------_=_NextPart_001_01C6F46E.6B18D12A
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

> > Well, because _ is a valid subroutine/variable name char, it would
> > require surrounding whitespace, at least in certain
> contexts. I believe that's what did it in. Nothing to do with
> readability/typability.
>
> They had already addressed that, tho.  Larry said in the
> relevant Apocalypse:
>
> > The only downside to that is the space between a variable
> name and the
> > operator is required. This is to be construed as a feature.

I chatted with Allison Randal at OSCON shortly after this decision was
made (because I liked the _). IIRC, she said that the desire for
orthogonality in Parrot influenced the decision to switch.

> So I dunno.  _ works well in TT2, as we see.  And anyways, if
> you're going to toss _, where did ~ come from?  Just seems
> like a desperate choice to me (i.e. "now, which piece of
> punctuation do we have left over ... ?").

I agree! Hey, we got the whole UTF-8 space to work with, don't we? How
about the ellipsis character "..." (0x2026) or an em dash "-" (0x2014).
Seem like suitable choices to me ;-)

------_=_NextPart_001_01C6F46E.6B18D12A
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD><TITLE></TITLE>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<META content=3D"MSHTML 6.00.2900.2963" name=3DGENERATOR></HEAD>
<BODY>
&gt; &gt; Well, because _ is a valid =
subroutine/variable=20
name char, it would &gt; &gt; require surrounding whitespace, at =
least in=20
certain &gt; contexts. I believe that's what did it in. Nothing to do =

with &gt; readability/typability. &gt; &gt; They had already =
addressed=20
that, tho.&nbsp; Larry said in the &gt; relevant =
Apocalypse: &gt; &gt;=20
&gt; The only downside to that is the space between a variable &gt; =
name and=20
the &gt; &gt; operator is required. This is to be construed as a=20
feature. I chatted with Allison Randal at OSCON shortly after =
this=20
decision was made (because I liked the _). IIRC, she said that the =
desire for=20
orthogonality in Parrot influenced the decision to switch. &gt; =
So I=20
dunno.&nbsp; _ works well in TT2, as we see.&nbsp; And anyways, =
if &gt;=20
you're going to toss _, where did ~ come from?&nbsp; Just seems &gt; =
like a=20
desperate choice to me (i.e. "now, which piece of &gt; punctuation do =
we have=20
left over ... ?"). I agree! Hey, we got the whole UTF-8 space to =
work=20
with, don't we? How about the ellipsis character "&#8230;" (0x2026) or =
an em dash "&#8212;"=20
(0x2014). Seem like suitable choices to me =
;-) </BODY></HTML>

------_=_NextPart_001_01C6F46E.6B18D12A--