On Fri Jun 08 06:56:27 2007, ptc wrote:
> In the file, config/inter/progs.pm there is the todo item associated
> with the following comment:
>
> # Find a working version of a program:
> # Try each alternative, until one works.
> # If none work, then set to null command.
> # XXX nee
# New Ticket Created by "Brad Gilbert"
# Please include the string: [perl #53924]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=53924 >
Fixed some typos in t/op/sysinfo.t
Index: t/op/sysinfo.t
=
Resolved by omission: We deleted this config step a few days ago.
kid51
Since this didn't make it to the mailing list -- this is now fixed
as of r27397.
Pm
On Thu, May 08, 2008 at 11:28:36AM -0700, Moritz Lenz wrote:
> Rakudo as of r27393 can't handle multiple declarations in a single "my":
>
> > my (@a, @b); say @a
> Scope not found for PAST::Var '@a'
We'll work on this one.
> > my @a, @b; say @a
> Scope not found for PAST::Var '@b'
Rakudo has
# New Ticket Created by Patrick R. Michaud
# Please include the string: [perl #53926]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=53926 >
This one is a bit obscure... but it's a bit of a rakudo blocker
at the moment for
Carl Mäsak cmasak-at-gmail.com |Perl 6| wrote:
Pm (>):
In Rakudo's case, we just haven't implemented read-only traits
on variables yet.
Goodie. I guessed as much.
But yes, I expect that it will be caught as
a compile-time error.
And do you agree it's reasonable to expect t
Andrew - thanks for looking at this and while I haven't read your patch
On Fri, May 9, 2008 at 1:38 PM, jerry gay <[EMAIL PROTECTED]> wrote:
> On Fri, May 9, 2008 at 10:27 AM, chromatic <[EMAIL PROTECTED]> wrote:
>> - I'm not sure how accurate or useful the discussion of formal roles is.
>>
On Friday 09 May 2008 10:38:22 jerry gay wrote:
> for the canonical list of parrot roles and responsibilities, see
> docs/project/roles_responsibilities.pod.
>
> you'll find platform porter listed there. listed as well is pumpking,
> which should be removed.
>
> i suggest the chapter text and the
On Fri, May 9, 2008 at 10:27 AM, chromatic <[EMAIL PROTECTED]> wrote:
> - I'm not sure how accurate or useful the discussion of formal roles is. For
> example, we seem to be doing fine without a pumpking, and this is the only
> place I've ever heard the term "platform porter"
>
for the canonical
On Friday 09 May 2008 05:59:43 Andrew Whitworth wrote:
> This is a documentation-only patch, no code is affected. The "book" in
> doc/book/ is out of date and I am working to rewrite and update it.
> This is a rewrite of the first chapter. I've fixed errors, updated old
> information, and expanded
# New Ticket Created by "Andrew Whitworth"
# Please include the string: [perl #53916]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=53916 >
This is a documentation-only patch, no code is affected. The "book" in
doc/book/ i
On Fri, May 09, 2008 at 05:09:31PM +0200, Carl Mäsak wrote:
> Pm (>):
> > In Rakudo's case, we just haven't implemented read-only traits
> > on variables yet.
>
> Goodie. I guessed as much.
>
> > But yes, I expect that it will be caught as
> > a compile-time error.
>
> And do you agree it's rea
TSa Thomas.Sandlass-at-barco.com |Perl 6| wrote:
E.g. sqrt(2) might return a special Inf that can be lazily
stringified to an arbitrary long sequence of digits of sqrt(2).
???
The sqrt(2) should be a Num of 1.414213562373 with the precision of the
native floating-point that runs at full spe
Pm (>):
> In Rakudo's case, we just haven't implemented read-only traits
> on variables yet.
Goodie. I guessed as much.
> But yes, I expect that it will be caught as
> a compile-time error.
And do you agree it's reasonable to expect this of every compiler?
// Carl
On Fri, May 09, 2008 at 03:02:28PM +0200, Carl Mäsak wrote:
> TSa (>):
> > sub bar ($x)
> > {
> >$x = 3; # error, $x is readonly
> >foo($x); # error, could hit rw Str
> > }
>
> By the way, I hope it's possible to make the assignment `$x = 3` to
> the read-only variable $x a compile-time
On Fri, May 9, 2008 at 6:03 AM, Will Coleda <[EMAIL PROTECTED]> wrote:
> After some administrative snafus, we've finally gotten Andrew's commit
> bit assigned!
>
> I have assigned him several tickets in RT as penance. ^_^
>
wonderful! as a point of introduction, andrew has provided a number of
qual
http://gcc.gnu.org/gcc-4.4/changes.html
I'm sure the intel specific AES acceleration will come in real handy. ;)
On Thu, May 08, 2008 at 10:39:29PM -0500, Andy Lester wrote:
> I've just built the 5/2/2008 snapshot of GCC 4.4 and Parrot builds
> fine on it. I wonder what new warning flags 4.4 h
HaloO,
Carl Mäsak wrote:
By the way, I hope it's possible to make the assignment `$x = 3` to
the read-only variable $x a compile-time error.
I hope so, too. The variable and its read-only constraint
is known at compile time and *not* dependend on the value
inside. How it came in there in the f
HaloO,
I wrote:
John M. Dlugosz wrote:
> I wrote a complete treatment of Inf support.
> Please take a look at "24.26 Infinite" on pages 116-119, and
> "3.11.3 Infinities" on pages 26-27.
I have a lot to say to that. Please give me time.
I find your treatment of Inf too Num centric. E.g. al
After some administrative snafus, we've finally gotten Andrew's commit
bit assigned!
I have assigned him several tickets in RT as penance. ^_^
Regards!
--
Will "Coke" Coleda
TSa (>):
> sub bar ($x)
> {
>$x = 3; # error, $x is readonly
>foo($x); # error, could hit rw Str
> }
By the way, I hope it's possible to make the assignment `$x = 3` to
the read-only variable $x a compile-time error.
In fact, I hope this to such a degree that I would like it to be part
HaloO,
I wrote:
class C does A does B {...} # enters C into WHAT space
my $y = C.new; # $y.WHAT =:= C
my $b <: B; # automatically re-typing container
my $a <: A; # means e.g. my A $a is autotype
$b = $y; # now $y.WHAT =:= B
$a = $y; # now $y.WHAT =:= (A&B)
This last assignm
# New Ticket Created by Moritz Lenz
# Please include the string: [perl #53904]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=53904 >
rakudo as of r27393
class Foo {
has $.a;
has $.b;
}
my $x = Foo.new(a => 1, b =
On Mi. 07. Mai 2008, 13:55:13, desertmax wrote:
> As discussed on IRC, I've replaced print "foo" print "\n" with say
> "foo". Furthermore, I've added tests for init and version, if GMP is not
> available and one test for version, if GMP is present.
> The constructor does not raise an exception anym
# New Ticket Created by Moritz Lenz
# Please include the string: [perl #53902]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=53902 >
Rakudo as of r27393 can't handle multiple declarations in a single "my":
> my (@a, @b);
2008/5/9 Andy Lester <[EMAIL PROTECTED]>:
> I've just built the 5/2/2008 snapshot of GCC 4.4 and Parrot builds fine on
> it. I wonder what new warning flags 4.4 has that I can exploit.
Does valgrind work now with 4.4?
freebsd rel-7 ports valgrind had problems with 4.3 and 4.2
--
Reini Urban
htt
HaloO,
John M. Dlugosz wrote:
TSa Thomas.Sandlass-at-barco.com |Perl 6| wrote:
It's called overload resolution. Perl 6 can't do
that at compile time unless *all* targets are
available as rw and readonly variants.
I don't follow that statement. Can you give an example?
multi sub foo (Int $i
28 matches
Mail list logo
