Author: larry
Date: Mon Oct 9 00:22:24 2006
New Revision: 12875
Modified:
doc/trunk/design/syn/S05.pod
Log:
P5's s[pat][repl] syntax is dead, now use s[pat] = repl
Modified: doc/trunk/design/syn/S05.pod
==
---
HaloO,
Stevan Little wrote:
I think that maybe we need to seperate the concept of roles as types
and roles as partial classes, they seem to me to be in conflict with
one another. And even they are not in conflict with one another, I
worry they will bloat the complexity of roles usage.
The
HaloO,
Jonathan Lang wrote:
TSa wrote:
Dispatch depends on a partial ordering of roles.
Could someone please give me an example to illustrate what is meant by
partial ordering here?
In addition to Matt Fowles explanation I would like to
give the following example lattice build from the
HaloO,
TSa wrote:
Note that the superclass interface of roles should be mostly inferred
from the usage of next METHOD. As such it is a useful guidance for
error reports in the class composition process.
Actually 'next METHOD' doesn't catch all superclass interface issues.
There is the simple
HaloO,
Stevan Little wrote:
I do not think method combination should be the default for role
composition, it would defeat the composeability of roles because you
would never have conflicts.
I don't get that. The type system would give compile time errors.
The current spec means that in case
HaloO,
TSa wrote:
Note that A = (A|B) (A|C) is the intersection type of A|B and A|C.
Note further that A|B is a subtype of A and B written A|B : A and
A|B : B and so on. Usually the A|B|C is called Bottom or some such.
I think it is the Whatever type of Perl6. It is the glb (greatest lower
Author: larry
Date: Mon Oct 9 08:34:36 2006
New Revision: 12933
Modified:
doc/trunk/design/syn/S02.pod
doc/trunk/design/syn/S05.pod
Log:
Quote and regex adverbs may now take only parentheses as brackets.
Modified: doc/trunk/design/syn/S02.pod
Author: larry
Date: Mon Oct 9 08:44:59 2006
New Revision: 12936
Modified:
doc/trunk/design/syn/S02.pod
Log:
bleah, typo from ENOCAFFEINE
Modified: doc/trunk/design/syn/S02.pod
==
--- doc/trunk/design/syn/S02.pod
I don't understand why having :bytes for things like s/// would be a
good thing.
A Str doesn't have bytes, just like how a Buf doesn't have characters.
To get bytes out of a Str, you need an encoding. There will be an
internal encoding, but exposing it in this way is probably just asking
for a
On Mon, Oct 09, 2006 at 11:40:09PM +0200, Juerd wrote:
: I don't understand why having :bytes for things like s/// would be a
: good thing.
:
: A Str doesn't have bytes, just like how a Buf doesn't have characters.
:
: To get bytes out of a Str, you need an encoding. There will be an
: internal
Author: larry
Date: Mon Oct 9 15:35:46 2006
New Revision: 12964
Modified:
doc/trunk/design/syn/S05.pod
Log:
!alpha is not the same as -alpha, spotted by putter++
Made some of the whitespace rules more explicit.
Modified: doc/trunk/design/syn/S05.pod
11 matches
Mail list logo
