> Maybe it's just me, but I would find $var much easier to read and
> understand than {{{var}}}.
>
Me too, even if my voice doesn't really counts (as I am not from WF).
Readability is very important thing that helps to re-use the code and to
make less bugs.
Dmitriy
__
Chad wrote:
> On Thu, Jul 9, 2009 at 2:35 PM, William Allen
> Simpson wrote:
>> {{{...}}} works, is easily distinguished from normal text, and BBedit
>> does a fine job keeping the braces balanced. I'm sure other editors, too.
>>
>> Anything else should wait for a general scripting language, as we'
On Thu, Jul 9, 2009 at 2:35 PM, William Allen
Simpson wrote:
> Aryeh Gregor wrote:
>> On Wed, Jul 8, 2009 at 8:56 PM, William Allen
>> Simpson wrote:
>>> Not sure, as I've been using Unix since late 1977, so my fingers mostly
>>> remember csh. The $ is something like "contents of variable".
>>
>> I
Aryeh Gregor wrote:
> On Wed, Jul 8, 2009 at 8:56 PM, William Allen
> Simpson wrote:
>> Not sure, as I've been using Unix since late 1977, so my fingers mostly
>> remember csh. The $ is something like "contents of variable".
>
> It's a way to distinguish variables from ordinary text. Shell
> scri
On Wed, Jul 8, 2009 at 8:56 PM, William Allen
Simpson wrote:
> Not sure, as I've been using Unix since late 1977, so my fingers mostly
> remember csh. The $ is something like "contents of variable".
It's a way to distinguish variables from ordinary text. Shell
scripts, like wikitext, don't requir
Aryeh Gregor wrote:
> On Wed, Jul 8, 2009 at 8:04 AM, William Allen
> Simpson wrote:
>> I'm not sure that would actually be parsed. And I'm no fan of leading $,
>> left over from the variety in PERL.
>>
>> PHP isn't a model syntax that we should employ.
>
> Didn't the Bourne shell use a $ prefix f
On Wed, Jul 8, 2009 at 8:04 AM, William Allen
Simpson wrote:
> I'm not sure that would actually be parsed. And I'm no fan of leading $,
> left over from the variety in PERL.
>
> PHP isn't a model syntax that we should employ.
Didn't the Bourne shell use a $ prefix for all variables, a decade
befor
Neil Harris wrote:
> In the spirit of supplying concrete examples, here are my proposed
> changes to the syntax of the existing language:
>
> * the existing {{{parm}}} or {{{parm|default}}} notation should be
> changed to ${parm} or ${parm|default}
>
I'm not sure that would actually be parsed.
Neil Harris wrote:
> * all newlines and other multiple whitespace characters within template
> source code should be regarded as reduced to single spaces, with
> explicit calls to {{newline}} and {{whitespace}} operators to generate
> explicit whitespace on output
>
Just to clarify this a bit
In the spirit of supplying concrete examples, here are my proposed
changes to the syntax of the existing language:
* the existing {{{parm}}} or {{{parm|default}}} notation should be
changed to ${parm} or ${parm|default}
* all newlines and other multiple whitespace characters within template
so
10 matches
Mail list logo
