On Thu, Jan 29, 2009 at 10:58:18PM -0800, Mark Lentczner wrote:
>> [STD, S03] slaughter of the LTM metatokens
>
> This cleans up the metaop scene quite a bit. Bravo!
>
> I went through STD.pm with a fine tooth comb again, to extract what I'd
> say about which operators were allowed to be meta'd b
Mark (>), Moritz (>>), Larry via commit bot (>>>):
>>> +PERL# Lexical symbols in the standard "perlude"
>>
>> Did you mean "prelude" instead?
>
> I took the quotation marks to indicate an intentional
> misspelling/coinage: "perl" + "prelude" = "perlude".
At which point one might ask o
pugs-comm...@feather.perl6.nl wrote:
In the abstract, Perl is written in Unicode, and has consistent Unicode
-semantics regardless of the underlying text representations.
+semantics regardless of the underlying text representations. By default
+Perl presents Unicode in "NFG" formation, where ea
On Fri, Jan 30, 2009 at 6:30 AM, Darren Duncan wrote:
> pugs-comm...@feather.perl6.nl wrote:
>>
>> By default Perl presents Unicode in "NFG" formation, where each grapheme
>> counts as
>> one character. A grapheme is what the novice user would think of as a
>> character in their normal everyday
On Fri, Jan 30, 2009 at 10:49:13AM +0100, Carl Mäsak wrote:
: Mark (>), Moritz (>>), Larry via commit bot (>>>):
: >>> +PERL# Lexical symbols in the standard "perlude"
: >>
: >> Did you mean "prelude" instead?
: >
: > I took the quotation marks to indicate an intentional
: > misspelling
On Fri, Jan 30, 2009 at 11:30 AM, Larry Wall wrote:
> We want something that comes
> outside your program, that is, a lexical scope that *surrounds* the
> file scope. We don't have a good word for that: circumlude? ambilude?
>[...]
> Or we could go with a more linguistic contextual metaphor. A
Larry Wall wrote:
> So I'm open to suggestions for what we ought to call that envelope
> if we don't call it the prelude or the perlude. Locale is bad,
> environs is bad, context is bad...the wrapper? But we have dynamic
> wrappers already, so that's bad. Maybe the setting, like a jewel?
> That
On Fri, Jan 30, 2009 at 08:30:25AM -0800, Larry Wall wrote:
> So anyway, just because other languages call it a prelude doesn't
> mean that we have to. Perl is the tail that's always trying to
> wag the dog...
>
> What is the sound of one tail wagging?
For my dog Sally, the sound of one tail wag
On Fri, Jan 30, 2009 at 03:30:02AM -0800, Darren Duncan wrote:
> pugs-comm...@feather.perl6.nl wrote:
>> In the abstract, Perl is written in Unicode, and has consistent Unicode
>> -semantics regardless of the underlying text representations.
>> +semantics regardless of the underlying text represen
On Fri, 2009-01-30 at 08:12 +0100, pugs-comm...@feather.perl6.nl wrote:
> @@ -103,7 +106,7 @@
> =item *
>
> POD sections may be used reliably as multiline comments in Perl 6.
> -Unlike in Perl 5, POD syntax now requires that C<=begin comment>
> +Unlike in Perl 5, POD syntax now lets you use C<=
On Fri, Jan 30, 2009 at 10:28:43AM -0800, Geoffrey Broadwell wrote:
: On Fri, 2009-01-30 at 08:12 +0100, pugs-comm...@feather.perl6.nl wrote:
: > @@ -103,7 +106,7 @@
: > =item *
: >
: > POD sections may be used reliably as multiline comments in Perl 6.
: > -Unlike in Perl 5, POD syntax now requ
Larry Wall wrote:
On Fri, Jan 30, 2009 at 03:30:02AM -0800, Darren Duncan wrote:
What's with this NFG / Normal Form G that you refer to? I don't see any
mention of that in http://unicode.org/reports/tr15/ ... did you mean NFC?
Nope, this is a Perl/Parrot idea. It started out with a notion of
12 matches
Mail list logo
