From: chromatic <[EMAIL PROTECTED]>
Date: Wed, 4 Oct 2006 22:33:07 -0700
It looks like the latest coroutine changes have uncovered a bug; now I can't
get Parrot to build. Here's the relevant message:
It's actually something I introduced (in continuation changes; coroutine
changes ar
# New Ticket Created by Bernhard Schmalhofer
# Please include the string: [perl #40455]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=40455 >
Hi,
since a while 'languages/dotnet' showed up as all red in unified
languages
Hi all,
I want to create a kind of bitvector object. Ideally, I'd like to inherit
from Array and then overload [],=, +,- etc.
I tried to overload the '+' operator, but I can't get it to work as a
method. Also, I'd like to overload the assignment operator.
Is that at all possible?
Below is my atte
On Wed, Oct 04, 2006 at 01:04:45PM -0700, chromatic wrote:
> On Wednesday 04 October 2006 12:48, jesse wrote:
>
> > Ok. So, I think what you're saying is that it's not a matter of "don't let
> > people write libraries that add strictures to code that uses those modules"
> > but a matter of "per
On Wed, Oct 04, 2006 at 12:43:04PM -0700, chromatic wrote:
> On Wednesday 04 October 2006 12:09, jesse wrote:
>
> > Perhaps I'm misunderstanding what you mean by "person writing the
> > program" and "person writing the libraries." In fact, I've _gotta_
> > be. I'd like to be able to put my str
HaloO,
Brad Bowman wrote:
Sam Vilain wrote:
This will be the same as requiring that a class implements a
method, except the method's name is infix:<==>(::T $self: T $other)
or some such.
Sure. The point is, how does a role designer mix in the x and y
coordinate attributes *and* augment the no
HaloO,
Larry Wall wrote:
Basically, all types do Package whenever they need an associated
namespace.
Great! This is how I imagined things to be. And the reason why
the :: sigil is also the separator of namespaces.
And most of the Package role is simply:
method postfix:<::> () { return
Author: larry
Date: Thu Oct 5 11:16:58 2006
New Revision: 12736
Modified:
doc/trunk/design/syn/S04.pod
Log:
Removed hash composers from line-ending curly rule entirely. Now a parsefail.
Modified: doc/trunk/design/syn/S04.pod
=
Author: larry
Date: Thu Oct 5 11:42:26 2006
New Revision: 12737
Modified:
doc/trunk/design/syn/S04.pod
Log:
"Bad dates..."
Modified: doc/trunk/design/syn/S04.pod
==
--- doc/trunk/design/syn/S04.pod(original)
S04 says:
A line ending with a closing brace "}", followed by nothing but whitespace or
comments, will terminate a statement if an end of statement can occur there.
That is, these two statements are equivalent:
my $x = sub { 3 }
my $x = sub { 3 };
Does this mean that
if $foo == 123 {
chromatic wrote:
jesse wrote:
> Ok. So, I think what you're saying is that it's not a matter of "don't let
> people write libraries that add strictures to code that uses those modules"
> but a matter of "perl should always give you enough rope to turn off any
> stricture imposed on you by externa
Hopefully the following will help. If I've missed the thrust of your
questions, feel free to disregard while someone else improves on my
answer :) I only overloaded the infix:<+> operator, but it should give
you an idea.
I would write the class comme ça:
use v6-alpha;
class Register {
has
Haha, that will teach me for trying to golf on public mailing lists.
It should actually read:
sub int2vec ($n) {
+<<(sprintf("%b",$n).split('')); # now I'm just golfing :-D
}
unless you only ever want to use it with the number 7.
-db.
- Original Message
From: David Bru
What if I import two modules, both of which export a 'foo' method?
IMHO, it would be nice if this sort of situation was resolved in a
manner similar to how role composition occurs: call such a conflict a
fatal error, and provide an easy technique for eliminating such
conflicts. One such techniqu
# New Ticket Created by "Paul Cochrane"
# Please include the string: [perl #40458]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=40458 >
Hi,
This patch gets the C-file coda test to pick up multiple occurrences
of the coda
On Thursday 05 October 2006 04:31, Bob Rogers wrote:
> It's actually something I introduced (in continuation changes; coroutine
> changes are still yet to come). r14845 should correct it. Sorry for
> the hassle.
Confirmed fixed! Thanks.
-- c
Karl Forner schrieb:
So in my opinion too this pmc should be rewritten. I'm ready to do it,
based
on my fixedbooleanarray implementation,
but before doing it I need some answers :
Yes, I've always why ResizableBooleanArray extends FixedBooleanArray and why
FixedBooleanArray is not simply a sp
Am Donnerstag, 5. Oktober 2006 01:49 schrieb Karl Forner:
>
> Whare the requirements/constraints of a ResizableBooleanArray ? e.g are
> unshift to be less frequent that shift ?
shift and unshift are both more unlikely than push/pop I presume. OTOH if a
user wants a bit queue, you have to deal wit
You've exactly got what's on my mind. But no one could know that, since
I haven't written it down yet. :)
We got several volunteers, so I'm going to spend some time talking with
them.
Allison
Adriano Ferreira wrote:
Among the features that cannot be missed in a transformation language
(and
S04 now reads:
==
However, a hash composer may never occur at the end of a line. If the
parser sees anything that looks like a hash composer at the end of
the line, it fails with "closing hash curly may not terminate line"
or some such.
my $hash = {
1 => { 2 => 3, 4 => 5 },
Jonathan Lang wrote:
What if I import two modules, both of which export a 'foo' method?
That's always fine unless they have exactly the same signature. In
general, that's not going to happen because the first parameter is
created from the invocant. Thus:
use HTML4;
use Math:
Jonathan Worthington schrieb:
Hi,
I've checked in the proposed bytecode PDD and also most of the changes
that I discussed with Allison earlier today. Feedback on it would be
greatly appreciated.
One thing that I noticed is the naming of the new field UUID.
||| The UUID is |
Aaron Sherman wrote:
Proposal: A sigil followed by [...] is always a composer for that type.
%[...]- Hash. Unicode: ⦃...⦄
@[...]- Array. Unicode: [...]
...
I left out ::, which is probably a mistake. Part of the elegance of
this, IMHO, is that it behaves the same for all sig
On 10/5/06, Aaron Sherman <[EMAIL PROTECTED]> wrote:
Proposal: A sigil followed by [...] is always a composer for that type.
%[...] - Hash. Unicode: ⦃...⦄
@[...] - Array. Unicode: [...]
? - Seq. Unicode: ⎣...⎤
&[...] - Code. Unicode: ⦕...⦖
|[...]
Am Donnerstag, 5. Oktober 2006 23:04 schrieb Bernhard Schmalhofer:
> Shouldn't this field be renamed to something like 'checksum' ? The term
> 'UUID' already has a specific meaning, http://en.wikipedia.org/wiki/UUID.
Indeed. But we probably want to have an UUID to identify
loaded .pasm/.pir/.pbc
Mark J. Reed wrote:
On 10/5/06, Aaron Sherman <[EMAIL PROTECTED]> wrote:
Proposal: A sigil followed by [...] is always a composer for that type.
%[...] - Hash. Unicode: ⦃...⦄
@[...] - Array. Unicode: [...]
? - Seq. Unicode: ⎣...⎤
&[...] - Code. Unicode:
Aaron Sherman wrote:
(updated based on followup conversations)
Proposal: A sigil followed by [...] is always a composer for that type.
%[...]- Hash.
@[...]- Array.
&[...]- Code.
|[...]- Capture. Identical to \(...).
$[...]- Scalar. Like item(...), but fo
Yes, I've always why ResizableBooleanArray extends FixedBooleanArray and
why
FixedBooleanArray is not simply a special case of ResizableBooleanArray.
Because a FixedBooleanArray is simpler, so that it may use less memory and
be implemented more efficiently I suppose.
Is there a real differenc
On 10/5/06, Leopold Toetsch <[EMAIL PROTECTED]> wrote:
Am Donnerstag, 5. Oktober 2006 01:49 schrieb Karl Forner:
>
> Whare the requirements/constraints of a ResizableBooleanArray ? e.g are
> unshift to be less frequent that shift ?
shift and unshift are both more unlikely than push/pop I presum
29 matches
Mail list logo
