On Thu, 2002-11-28 at 14:59, Michael Lazzaro wrote:
> But my worries are that we could not keep P6L sufficiently focused,
> resulting in an even *bigger* tangle of threads; that we can't really
> *have* the discussions without posting the proposed documentation too;
> and that P6L would not respond
"Bryan C. Warnock" wrote:
>
> On Tue, 2002-11-26 at 13:36, Michael Lazzaro wrote:
> > The main difference is that p6-docs is intended to move very narrowly
> > from topic to topic, in a roughly predetermined order, focusing on each
>
> But not to move faster than the design of the language.
Yeah
"Bryan C. Warnock" <[EMAIL PROTECTED]> writes:
> Be kind to Piers.
Ah... Yes do. I need all the kindness I can get.
--
Piers
"It is a truth universally acknowledged that a language in
possession of a rich syntax must be in need of a rewrite."
-- Jane Austen?
On Tue, 2002-11-26 at 13:36, Michael Lazzaro wrote:
> The main difference is that p6-docs is intended to move very narrowly
> from topic to topic, in a roughly predetermined order, focusing on each
But not to move faster than the design of the language.
> one until the more dedicated members st
On Tue, 2002-11-26 at 09:17, Garrett Goebel wrote:
>
> p6d exists to document the language. A task which consists of going over the
> A&E's and Larry's posts to p6l, etc. and flushing them out into
> deliverables:
>
> o Perl6/Parrot regression tests
> o Language Specification derived from tests
Larry Wall writes:
> Note that the "true" property is not the same as the "true" function.
> This tells me that properties may need their own namespace distinct
> from either subs or classes. (We've talked about defining properties
> as subs or classes, but either way is problematic. If we ha
On Tuesday, November 26, 2002, at 09:47 AM, Larry Wall wrote:
: > (3) Context. How to determine it, how to force it. Hypothesis:
There
: > is a one-to-one relationship between Type and Context, such that
there
: > is a context that matches every type, and a type that matches every
: > contex
On Monday, November 25, 2002, at 04:46 PM, Bryan C. Warnock wrote:
On Mon, 2002-11-25 at 14:25, Michael Lazzaro wrote:
(2) The behavior of an explicit bool type, _if_ one exists, that
stores "truth", not "value". Such that C
stores true, not 0, and does so in "the most efficient way".
If yo
On Mon, Nov 25, 2002 at 07:46:57PM -0500, Bryan C. Warnock wrote:
: Should an explicit bool type be part of the language? If so, how should
: it work? C storing only a truth property but
: no value makes little sense in the context of the larger language. So
: does handling truth as something oth
On Tue, Nov 26, 2002 at 08:52:52AM -0600, Garrett Goebel wrote:
: On Mon, 2002-11-25 at 14:25, Michael Lazzaro wrote:
: > (2) The behavior of an explicit bool type, _if_ one exists,
: > that stores "truth", not "value". Such that C = (0 but true)> stores true, not 0, and does so in "the
: > most
On Mon, 2002-11-25 at 14:25, Michael Lazzaro wrote:
> (2) The behavior of an explicit bool type, _if_ one exists,
> that stores "truth", not "value". Such that C = (0 but true)> stores true, not 0, and does so in "the
> most efficient way".
There is no explicit bool type.
Larry Wall wrote:
>
>
From: Bryan C. Warnock [mailto:[EMAIL PROTECTED]]
>
> If you don't already know whether it exists, or how it will
> roughly work (lexically), you shouldn't be discussing it on
> p6d. Kicked back to p6l.
[...]
> and again... what's the scope of p6d
p6d exists to document the language. A task whi
On Mon, 2002-11-25 at 14:25, Michael Lazzaro wrote:
> (2) The behavior of an explicit bool type, _if_ one exists, that stores
> "truth", not "value". Such that C stores
> true, not 0, and does so in "the most efficient way".
If you don't already know whether it exists, or how it will roughly wo
13 matches
Mail list logo