# New Ticket Created by NotFound
# Please include the string: [perl #55590]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=55590 >
This patch solves the casting problems that breaks or generates
warnings in src/io/io_unix.c
> Well, if I had RTFM 'perldoc File::Temp' correctly, I wouldn't have
> gotten the arguments wrong.
>
> Sorry for the confusion.
>
Sometimes, you just have to explain it to the bear before you understand.
:-)*
--
Email and shopping with the feelgood factor!
55% of income to good causes. http
On Tue, Jun 10, 2008 at 06:00:39AM -0700, Will Coleda via RT wrote:
> Interesting. I tried to duplicate this error by removing my platform's
> hints file and re-running. I get the message you describe, but then
> Configure.pl completes, and at the -end-, gracefully says:
>
> During configuration t
# New Ticket Created by Ron Schmidt
# Please include the string: [perl #55594]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=55594 >
Perl 5 allows empty semicolon terminated statements. perl6 currently
allows for empty c
On Tue, Jun 10, 2008 at 06:00:39AM -0700, Will Coleda via RT wrote:
> Your workaround, btw, is probably:
>
> touch config/init/hints/hurd.pm
That actually complained about a non-true value. The correct
incantation turned out to be:
echo '1;' > config/init/hints/gnu.pm
The Configure.pl step
On Tue, Jun 10, 2008 at 01:07:45PM -0700, Ron Schmidt wrote:
> Perl 5 allows empty semicolon terminated statements. perl6 currently
> allows for empty closures but treats a semicolon that follows nothing or
> whitespace as a syntax error. The attached patch to grammar.pg provides
> a fix for t
Author: larry
Date: Wed Jun 11 14:09:40 2008
New Revision: 14547
Modified:
doc/trunk/design/syn/S03.pod
Log:
change most left-associative short-circuit ops to list-associative
x and xx are now left associative
define what associativity means for unary ops
Modified: doc/trunk/design/syn/S03.p
... is cancelled, too many of us are going to be at YAPC::NA.
See everyone there, or at #parrotsketch in two weeks.
--
Will "Coke" Coleda
On Wed, Jun 11, 2008 at 02:09:41PM -0700, [EMAIL PROTECTED] wrote:
> +Note that these differ:
> +
> +$min ..^ $max$ min .. $max-1
> +$min .. ^$max# $min .. (0..$max-1)
The punctuation looks a little funny on the first line. Also, are
$min ..^ $max and $min .. $max-1 really the sam
# New Ticket Created by Vasily Chekalkin
# Please include the string: [perl #55620]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=55620 >
Hello.
Trivial reproducible bug: in rakudo 'say 1 ~~ Perl6Scalar'.
There is patch
Seg, 2008-06-09 às 17:51 -0700, Larry Wall escreveu:
> On Sat, Jun 07, 2008 at 09:49:03PM +0100, Daniel Ruoso wrote:
> : 2) Assume the capture-translation and define that
> : $foo.HOW.can($foo,'bar') keeps the $how as the invocant and must receive
> : the referring object as first argument.
> I pre
Another attempt: this is a minimalistic change that does not broke any
test in parrot nor in rakudo, and can avoid segfaulting in other related
usages.
Index: src/pmc/namespace.pmc
===
--- src/pmc/namespace.pmc (revisión: 28239)
+++
# New Ticket Created by NotFound
# Please include the string: [perl #55640]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=55640 >
I've found a bug in oo_get_class, it segfaults when calling pmc_type
with a NULL STIRNG *
T
On Mie. Jun. 11 06:48:06 2008, bacek wrote:
> Trivial reproducible bug: in rakudo 'say 1 ~~ Perl6Scalar'.
>
> There is patch for src/ops/object.ops
I tried another way: less checks, not more. See attached patch.
$ ./perl6 -e'say 1 ~~ Perl6Scalar'
Null PMC access in invoke()
current instr.: 'inf
On Wednesday 11 June 2008 12:48:51 NotFound via RT wrote:
> Another attempt: this is a minimalistic change that does not broke any
> test in parrot nor in rakudo, and can avoid segfaulting in other related
> usages.
This one is my favorite too.
-- c
On Wednesday 11 June 2008 14:44:34 NotFound wrote:
> I've found a bug in oo_get_class, it segfaults when calling pmc_type
> with a NULL STIRNG *
>
> This short pir code shows the problem:
>
> .sub main
> $P0= get_root_namespace
> $P1= get_class $P0
> .end
>
> The attached patch fixes it.
What
Author: larry
Date: Wed Jun 11 16:26:27 2008
New Revision: 14548
Modified:
doc/trunk/design/syn/S03.pod
Log:
clarification of reduced short-circuit ops
Modified: doc/trunk/design/syn/S03.pod
==
--- doc/trunk/design/s
Author: larry
Date: Wed Jun 11 16:49:17 2008
New Revision: 14549
Modified:
doc/trunk/design/syn/S03.pod
Log:
Fixes suggested by Ryan++
Modified: doc/trunk/design/syn/S03.pod
==
--- doc/trunk/design/syn/S03.pod
On Thu, Jun 12, 2008 at 1:23 AM, chromatic <[EMAIL PROTECTED]> wrote:
> What's it look like when patching pmc_type to deal with NULL STRING *? I'm
> not saying that's the best option; I'm just looking at the alternatives.
We must change his signature to do that. I tried the mininal change.
--
On Wed, Jun 11, 2008 at 04:49:18PM -0700, [EMAIL PROTECTED] wrote:
> -$min ..^ $max$ min .. $max-1
> -$min .. ^$max# $min .. (0..$max-1)
> +0 ..^ 10 # 0 .. 9
> +0 .. ^10 # 0 .. (0..9)
Ah, I should have been more specific - I meant that, since ~~ treats
Ranges as continuous
On Wed, Jun 11, 2008 at 08:20:41PM -0400, Ryan Richter wrote:
: On Wed, Jun 11, 2008 at 04:49:18PM -0700, [EMAIL PROTECTED] wrote:
: > -$min ..^ $max $ min .. $max-1
: > -$min .. ^$max # $min .. (0..$max-1)
: > +0 ..^ 10 # 0 .. 9
: > +0 .. ^10 # 0 .. (0..9)
:
: Ah, I
Author: larry
Date: Wed Jun 11 17:34:50 2008
New Revision: 14550
Modified:
doc/trunk/design/syn/S05.pod
Log:
fixed "samebase" illogic pointed out by moritz++
Modified: doc/trunk/design/syn/S05.pod
==
--- doc/trunk/de
Author: larry
Date: Wed Jun 11 17:53:27 2008
New Revision: 14551
Modified:
doc/trunk/design/syn/S05.pod
Log:
added <...> et al. as suggested by ruoso++
Modified: doc/trunk/design/syn/S05.pod
==
--- doc/trunk/design/s
On Fri Jul 13 09:58:33 2007, bernhard wrote:
> There are several config probes that are only used for language
> implementations.
> Examples are config/auto/m4.pm and config/auto/python.pm.
>
> In order to improve the seperation of concerns, these probes should be
> moved to a
> separate directo
It appears that this ticket was re-opened after some RT bookkeeping
problems, but there doesn't appear to be any reason to keep it open. Am
resolving it once again.
On Tuesday 10 June 2008 12:05:18 NotFound wrote:
> This patch solves the casting problems that breaks or generates
> warnings in src/io/io_unix.c allowing clean compiling with C or C++,
> with or without --optimize.
Applied in r28251.
> Also drops the const in argv in several main and main-alike
26 matches
Mail list logo
