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
==
---
At 12:26 04/10/2006 -0700, you wrote:
# New Ticket Created by Bernhard Schmalhofer
# Please include the string: [perl #40455]
# in the subject line of all future correspondence about this issue.
# URL: http://rt.perl.org/rt3/Ticket/Display.html?id=40455
Hi,
since a while 'languages/dotnet'
At 12:26 04/10/2006 -0700, you wrote:
# New Ticket Created by Bernhard Schmalhofer
# Please include the string: [perl #40455]
# in the subject line of all future correspondence about this issue.
# URL: http://rt.perl.org/rt3/Ticket/Display.html?id=40455
Hi,
since a while 'languages/dotnet'
Hi all,
I was having a poke around in DEPRECATED.pod and I've got a couple of
questions about the items therein:
.imc file extension paragraph:
There aren't any .imc files in parrot anymore as far as I can tell.
So, should this paragraph be in DEPRECATED.pod anymore? If not, I can
supply a
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
Parrot Bug Summary
http://rt.perl.org/rt3/NoAuth/parrot/Overview.html
Generated at Mon Oct 9 13:15:14 2006 GMT
---
* Numbers
* New Issues
* Overview of Open Issues
* Ticket Status By Version
* Requestors with
# New Ticket Created by Paul Cochrane
# Please include the string: [perl #40477]
# in the subject line of all future correspondence about this issue.
# URL: http://rt.perl.org/rt3/Ticket/Display.html?id=40477
Hi,
This patches the perl scripts which output a C-code coda when they
output
# New Ticket Created by Paul Cochrane
# Please include the string: [perl #40480]
# in the subject line of all future correspondence about this issue.
# URL: http://rt.perl.org/rt3/Ticket/Display.html?id=40480
Hi,
This patch ensures that when platform.c and platform.h are generated,
that
# New Ticket Created by Paul Cochrane
# Please include the string: [perl #40476]
# in the subject line of all future correspondence about this issue.
# URL: http://rt.perl.org/rt3/Ticket/Display.html?id=40476
Hi,
Recently I found some .pm files with dos line endings. This patch
changes
# New Ticket Created by Paul Cochrane
# Please include the string: [perl #40475]
# in the subject line of all future correspondence about this issue.
# URL: http://rt.perl.org/rt3/Ticket/Display.html?id=40475
Hi,
PMC files are just C-language files in a sense, right? If so, then
here's a
# New Ticket Created by Paul Cochrane
# Please include the string: [perl #40479]
# in the subject line of all future correspondence about this issue.
# URL: http://rt.perl.org/rt3/Ticket/Display.html?id=40479
Hi,
This patch adds the C-code coda to the autogenerated C language code,
and
# New Ticket Created by Paul Cochrane
# Please include the string: [perl #40482]
# in the subject line of all future correspondence about this issue.
# URL: http://rt.perl.org/rt3/Ticket/Display.html?id=40482
Hi,
This patch adds a new policy for the Parrot Perl::Critic tests, namely
to
Hi,
It's not that easy to contribute to parrot development.
I got into that by picking a TODO task about *BooleanArrays, that seemed
appropriate for a Parrot newbie that
knows a bit about algorithmics and Data structures.
Answering one of my mail, Bernhard raised the question of using a common
Hi all,
In r14862, Configure.pl throws an error when processing the Manifest.
The error is:
Checking MANIFEST...No such file: ext/Parrot-Embed/Embed.xs
Ack, some files were missing! I can't continue running
without everything here. Please try to find the above
files and then try running
On 10/9/06, Karl Forner [EMAIL PROTECTED] wrote:
Hi,
It's not that easy to contribute to parrot development.
I got into that by picking a TODO task about *BooleanArrays, that seemed
appropriate for a Parrot newbie that
knows a bit about algorithmics and Data structures.
thank you for your
On 10/9/06, Paul Cochrane [EMAIL PROTECTED] wrote:
Hi all,
In r14862, Configure.pl throws an error when processing the Manifest.
The error is:
Checking MANIFEST...No such file: ext/Parrot-Embed/Embed.xs
Ack, some files were missing! I can't continue running
without everything here. Please
On Oct 9, 2006, at 5:51 AM, Paul Cochrane (via RT) wrote:
# New Ticket Created by Paul Cochrane
# Please include the string: [perl #40482]
# in the subject line of all future correspondence about this issue.
# URL: http://rt.perl.org/rt3/Ticket/Display.html?id=40482
Hi,
This patch adds a
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
# New Ticket Created by Paul Cochrane
# Please include the string: [perl #40483]
# in the subject line of all future correspondence about this issue.
# URL: http://rt.perl.org/rt3/Ticket/Display.html?id=40483
Hi,
This patch uncuddles the else's in the C source, and makes the
Will,
They're all coding standards. I say leave the Coda where it is, and
put this in the same grouping as 'use warnings' (i.e.
'TestingAndDebugging').
Ok, see attached patch.
Also, instead of checking for /usr/local and then reporting a
violation, switch it. Check for the *allowed* version,
On Oct 9, 2006, at 4:51 AM, Paul Cochrane (via RT) wrote:
# New Ticket Created by Paul Cochrane
# Please include the string: [perl #40482]
# in the subject line of all future correspondence about this issue.
# URL: http://rt.perl.org/rt3/Ticket/Display.html?id=40482
Hi,
This patch adds a
On Oct 9, 2006, at 11:50 AM, Paul Cochrane wrote:
Will,
They're all coding standards. I say leave the Coda where it is, and
put this in the same grouping as 'use warnings' (i.e.
'TestingAndDebugging').
Ok, see attached patch.
This one is still a false negative on #!perl -Tw and is a false
Am Montag, 9. Oktober 2006 05:12 schrieb chromatic:
I'm experimenting with better forms of OO in PIR. I want to add a
get_parents() method on the Class PMC. Normally, I'd do something like the
attached patch, but the attached example file I use for testing shows that
it doesn't work for me.
Am Montag, 9. Oktober 2006 16:26 schrieb Karl Forner:
AND YET OTHER QUESTIONS
* What is the intended usage, or in other words, the usefulness of the
*BooleanArrays ?
A *BooleanArray *does* array[1] and it's storage size is one bit per item.
[1] the current array interface isn't much more
Paul Cochrane schrieb:
Hi all,
I was having a poke around in DEPRECATED.pod and I've got a couple of
questions about the items therein:
.imc file extension paragraph:
There aren't any .imc files in parrot anymore as far as I can tell.
So, should this paragraph be in DEPRECATED.pod anymore?
# New Ticket Created by chromatic
# Please include the string: [perl #40490]
# in the subject line of all future correspondence about this issue.
# URL: http://rt.perl.org/rt3/Ticket/Display.html?id=40490
Given this code:
.sub 'main' :main
.local pmc args
args = new .Hash
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
From: Bob Rogers [EMAIL PROTECTED]
Date: Mon, 2 Oct 2006 20:54:22 -0400
This weekend's project (committed as r14830) makes continuations
capture the dynamic environment so that they can restore it properly on
invocation. This makes it possible for multiple continuations to
js.pg in languages/ecmascript/src compiles just fine with pgc. But it
gives a Null PMC access error while using the compiled pir file. Is
it a pge bug?
$ cd languages/ecmascript/src
$ cat main.pir
.include 'errors.pasm'
.sub _main :main
.param pmc args
.local string source_code,
36 matches
Mail list logo
