[perl #57656] [PROPOSAL][PIR] change PIR sugar for concat into ".." (or something else)

# New Ticket Created by Klaas-Jan Stol # Please include the string: [perl #57656] # in the subject line of all future correspondence about this issue. # http://rt.perl.org/rt3/Ticket/Display.html?id=57656 > hi, the "." has different meanings in PIR: 1. to separate object and method in a met

[perl #57668] [BUG][PATCH] Iterate through the current namespace causes a segfault

# New Ticket Created by François PERRAD # Please include the string: [perl #57668] # in the subject line of all future correspondence about this issue. # http://rt.perl.org/rt3/Ticket/Display.html?id=57668 > The patch contains a test case that exhibits the problem. François. Index: t/pmc/nam

[perl #57680] [CAGE] Problems in find_write_record

# New Ticket Created by Andrew Whitworth # Please include the string: [perl #57680] # in the subject line of all future correspondence about this issue. # http://rt.perl.org/rt3/Ticket/Display.html?id=57680 > in src/stm/backend.c:find_write_record() there are a few cleanup notes: FIXME check

[perl #57676] [CAGE] Check for shared status of STM handle

# New Ticket Created by Andrew Whitworth # Please include the string: [perl #57676] # in the subject line of all future correspondence about this issue. # http://rt.perl.org/rt3/Ticket/Display.html?id=57676 > In src/stm/backend.c:Parrot_STM_mark_pmc_handle(), there is the following comment:

[perl #57678] [CAGE] Poor Man's Deadlock Detection

# New Ticket Created by Andrew Whitworth # Please include the string: [perl #57678] # in the subject line of all future correspondence about this issue. # http://rt.perl.org/rt3/Ticket/Display.html?id=57678 > In src/stm/backend.c:wait_for_version() there are a few XXX FIXME items: This algor

Re: [perl #57636] [TODO][PDD19] Document the reason for :unique_reg flag

On Wed, Aug 6, 2008 at 8:30 PM, Jonathan Worthington <[EMAIL PROTECTED]>wrote: > Will Coleda wrote: > >> Can you describe a situation where this occurs that isn't a bug in the >> register allocator? >> >> > Yes. IIRC, it was added when I was working on the .Net bytecode translator, > and it needed

[perl #57690] [BUG] make headerizer breaks build

# New Ticket Created by Andrew Whitworth # Please include the string: [perl #57690] # in the subject line of all future correspondence about this issue. # http://rt.perl.org/rt3/Ticket/Display.html?id=57690 > "make headerizer" appears to be screwing up the build. When I run make headerizer, i

[svn:parrot-pdd] r30081 - trunk/docs/pdds

Author: infinoid Date: Wed Aug 6 21:32:18 2008 New Revision: 30081 Modified: trunk/docs/pdds/pdd13_bytecode.pod Log: [docs/pdds/pdd13] Add the ability to delete a segment from a PackfileDirectory, per my discussion with jonathan++ on this subject. Modified: trunk/docs/pdds/pdd13_bytecode.po

[perl #57536] [BUG] Segfault in Parrot_memalign during shootout test 19 on 64-bit Intel OS X build

I've stopped the crashes that appear related to this on my box with the attached patch. config/gen/platform/darwin/memalign.c has a few unsigned variables that were being implicitly handled as (32-bit) ints, those variables are actually used as (or in the calculation of) memory addresses. N

[perl #57536] [BUG] Segfault in Parrot_memalign during shootout test 19 on 64-bit Intel OS X build

On Sat Aug 02 14:38:57 2008, tetragon wrote: > Using a lightly modified config (RT#57532), I got parrot to build as a > 64-bit Intel binary on OS X. One of a series of segfaults encountered > appears to be triggered in Parrot_memalign in > config/gen/platform/darwin/memalign.c (if gdb is to be bel

[perl #57700] [PATCH] Fix 64-bit Mac OS X Build

# New Ticket Created by chromatic # Please include the string: [perl #57700] # in the subject line of all future correspondence about this issue. # http://rt.perl.org/rt3/Ticket/Display.html?id=57700 > Based on a comment from Seneca in IRC earlier tonight, I'd like to get feedback from Mac O

Re: adverbs o operators

Larry Wall larry-at-wall.org |Perl 6| wrote: > As for > marking each op individually, it might be possible if we add a > whitespace dependency between "lt:lc" and "lt :lc", but 1 ..:by(2) 100 > is pretty ugly. > > Larry So do they have to go at the end of the whole expression in the current gram

Humorous but serious article

See my latest creation at

Another adverb on operator question

What about adverbs on reduction operators? [lt :lc] $a,$b,$c # all in decreasing order --John

Reason for attributes.t fail

Hi, Rakudo is currently failing t\spec\S12-class\attributes.t. This turns out not to be an issue with attributes, but rather exceptions. The test does: my $c = Counter.new(); try { $c.x } ok($!, 'no public accessor for private attribute'); And fails because the Exception PMC does not impl

[svn:parrot-pdd] r30083 - trunk/docs/pdds

Author: kjs Date: Thu Aug 7 03:35:11 2008 New Revision: 30083 Modified: trunk/docs/pdds/pdd19_pir.pod Log: [pdd19] add description for binary relational operators in = section. Modified: trunk/docs/pdds/pdd19_pir.pod ==

Fwd: [perl #57656] [PROPOSAL][PIR] change PIR sugar for concat into ".." (or something else)

[this message was not sent to list, which it seems it should have; hence the forward.] -- Forwarded message -- From: Andrew Whitworth via RT <[EMAIL PROTECTED]> Date: Thu, Aug 7, 2008 at 12:11 AM Subject: [perl #57656] [PROPOSAL][PIR] change PIR sugar for concat into ".." (or somet

time op inconsistent on Win32

Hi, I've just been looking at the time op, and what it returns is somewhat platform specific. * On Win32, it's the number of seconds since January 1, 1601 * In other codepaths, it appears to be the number of seconds since January 1, 1970. I'm thinking we should correct the Win32 version to

Re: [perl #57636] [TODO][PDD19] Document the reason for :unique_reg flag

On Wed, Aug 6, 2008 at 3:30 PM, Jonathan Worthington <[EMAIL PROTECTED]> wrote: > Will Coleda wrote: >> >> Can you describe a situation where this occurs that isn't a bug in the >> register allocator? >> > > Yes. IIRC, it was added when I was working on the .Net bytecode translator, > and it needed

S29 - Time

Hi, S29 says: "Returns a |Time| object. There are a number of uses for this object, all of which can be found in the documentation for |Time|." However, I don't see that documentation in S29, and have taken a browse around the Pugs repository and don't see any sign of it there either. Am I

[perl #57700] [PATCH] Fix 64-bit Mac OS X Build

As expected, no harm done on 32-bit PPC OS X 10.4. Since people are looking at patches for Darwin, let me remind you of these open tickets: http://rt.perl.org/rt3/Ticket/Display.html?id=49226 http://rt.perl.org/rt3/Ticket/Display.html?id=52212 (another Seneca patch) http://rt.perl.org/rt3/Ticke

[perl #57690] [BUG] make headerizer breaks build

For reference, here's what I got last night on Linux after a make realclean, svn up and perl Configure.pl. $ make headerizer && make /usr/local/bin/perl tools/build/headerizer.pl src/string.o src/ops/core_ops.o src/ops/core_ops_switch.o src/atomic/gcc_x86.o src/builtin.o src/byteorder.o src/charse

Re: [perl #57636] [TODO][PDD19] Document the reason for :unique_reg flag

Will Coleda wrote: Being allowed to poke inside your caller's register set seems... evil? It's the Parrot equivalent of the .Net CLR allowing you to take references to stuff in caller's stack frames. Can you provide a working PIR example that shows this functionality? It was implemente

Re: [perl #57690] [BUG] make headerizer breaks build

On Thu, Aug 7, 2008 at 7:53 AM, James Keenan via RT <[EMAIL PROTECTED]> wrote: > For reference, here's what I got last night on Linux after a make > realclean, svn up and perl Configure.pl. > > > > So I never got to 'make' per se; the problem is in > tools/build/headerizer.pl's action. > make hea

Re: [perl #57636] [TODO][PDD19] Document the reason for :unique_reg flag

On Thu, Aug 7, 2008 at 12:45 PM, Will Coleda <[EMAIL PROTECTED]> wrote: > On Wed, Aug 6, 2008 at 3:30 PM, Jonathan Worthington <[EMAIL PROTECTED]> > wrote: > > Will Coleda wrote: > >> > >> Can you describe a situation where this occurs that isn't a bug in the > >> register allocator? > >> > > > >

Re: [perl #57636] [TODO][PDD19] Document the reason for :unique_reg flag

On Thu, Aug 7, 2008 at 8:10 AM, Klaas-Jan Stol <[EMAIL PROTECTED]> wrote: > > > On Thu, Aug 7, 2008 at 12:45 PM, Will Coleda <[EMAIL PROTECTED]> wrote: >> >> On Wed, Aug 6, 2008 at 3:30 PM, Jonathan Worthington <[EMAIL PROTECTED]> >> wrote: >> > Will Coleda wrote: >> >> >> >> Can you describe a sit

Re: [perl #57690] [BUG] make headerizer breaks build

On Thu, Aug 7, 2008 at 2:06 PM, Will Coleda <[EMAIL PROTECTED]> wrote: > make headerizer is trying to operate on files generated by make. Given > that it's supposed to be updating the header files based on the C > sources, this seems vaguely reasonable, so I would suggest that the > problem is act

Re: [perl #57636] [TODO][PDD19] Document the reason for :unique_reg flag

Will Coleda wrote: So, again, do we in parrot want to support the ability to dig into our callers register set and pull out a particular register since we have no way to say which register that is when we're using PIR? Even unique_reg just says 'the register doesn't change', not "it's PMC registe

Re: [perl #57636] [TODO][PDD19] Document the reason for :unique_reg flag

On Thu, Aug 7, 2008 at 1:33 PM, Jonathan Worthington <[EMAIL PROTECTED]>wrote: > Will Coleda wrote: > >> So, again, do we in parrot want to support the ability to dig into our >> callers register set and pull out a particular register since we have >> no way to say which register that is when we'r

Re: [perl #57636] [TODO][PDD19] Document the reason for :unique_reg flag

Klaas-Jan Stol wrote: I think basically the question remans; is there any way we could do without the :unique_reg? Yes: 1) Add the reference-taking op and register reference PMC to the Parrot core. 2) Make IMCC specially aware of this op so that it never re-uses this register. Thanks,

Re: [perl #57398] Actually assigning to a read-only variable in rakudo causes parrot to segfault

jonathan++ pointed out that the two examples here are identical. The second one should be $ ./perl6 -e 'sub a($x) { $x = 5 }; a(7)' which segfaults as described.

Re: new article, "A Romp Through Infinity"

TSa Thomas.Sandlass-at-barco.com |Perl 6| wrote: As I recall, it can handle the concept of Inf-1 etc. Yes. But the Hyperreals do the same and stay within the realm of set theory. I'm not sure. A quick reading indicates that ⋆ℝ contains "infinitely large" numbers that maintain the properti

Re: [perl #57690] [BUG] make headerizer breaks build

On Thu, Aug 7, 2008 at 8:21 AM, NotFound <[EMAIL PROTECTED]> wrote: > On Thu, Aug 7, 2008 at 2:06 PM, Will Coleda <[EMAIL PROTECTED]> wrote: > >> make headerizer is trying to operate on files generated by make. Given >> that it's supposed to be updating the header files based on the C >> sources, t

[perl #57694] You are nominated for an Associates

Spam -- Reini Urban

Re: new article, "A Romp Through Infinity"

On Thu, Aug 7, 2008 at 3:19 PM, John M. Dlugosz <[EMAIL PROTECTED]> wrote: > I'm not sure. A quick reading indicates that ⋆ℝ contains "infinitely large" > numbers that maintain the properties of addition, but that is not the same > as "infinity". Well *R is a field that has infinitely large and

Re: [perl #57636] [TODO][PDD19] Document the reason for :unique_reg flag

On Thu, Aug 7, 2008 at 5:44 AM, Jonathan Worthington <[EMAIL PROTECTED]> wrote: > Klaas-Jan Stol wrote: >> >> I think basically the question remans; is there any way we could do >> without the :unique_reg? >> > Yes: > > 1) Add the reference-taking op and register reference PMC to the Parrot > core.

Re: new article, "A Romp Through Infinity"

HaloO, John M. Dlugosz wrote: The proposed Infinite class (see the thread I started on 4/25/2008) does handle transfinite cardinals. Do you mean the thread called "The Inf type" where I replied to your post of a version of your specdoc? My concern with the approach you take there is to base it

Re: Humorous but serious article

HaloO, John M. Dlugosz wrote: See my latest creation at Nice write-up! You say that there's no syntax for refering to a multi as a whole. But is that not simply the short name? E.g. infix:<+> is the multi of all targets in a scope. You need infix:<+>

[perl #57710] Parrot segfaults after subtype type check fails

# New Ticket Created by "Carl Mäsak" # Please include the string: [perl #57710] # in the subject line of all future correspondence about this issue. # http://rt.perl.org/rt3/Ticket/Display.html?id=57710 > r30087: $ ./perl6 -e 'subset A of Int where 1; my A $a = 1' # this works $ ./perl6 -e 's

Re: [perl #57636] [TODO][PDD19] Document the reason for :unique_reg flag

On Thu, Aug 7, 2008 at 10:04 AM, jerry gay <[EMAIL PROTECTED]> wrote: > On Thu, Aug 7, 2008 at 5:44 AM, Jonathan Worthington <[EMAIL PROTECTED]> > wrote: >> Klaas-Jan Stol wrote: >>> >>> I think basically the question remans; is there any way we could do >>> without the :unique_reg? >>> >> Yes: >>

Re: Humorous but serious article

Hi >See my latest creation at A "modern" decendent of APL is J http://www.jsoftware.com/ http://www.jsoftware.com/jwiki/FrontPage Regards, Todd Olson

windows XP copyfile

I'm trying to do a Perl script (PC has Perl5 installed) in a BAT file which will open the CMD prompt, interact with the user and copy files from one location to other directories. Does anyone know how to "dir" the files in a directory into an array and sort by date and return the ones within the p

[perl #57422] Assigning to instance hashes,arrays fails

Hi, As of r30090, the following: -- class Foo { has %.bar is rw; method set_bar { %.bar = 'baz'; } } my $foo = Foo.new; $foo.set_bar(); my %s = $foo.bar; say %s; -- Now prints "baz". Also this: -- class Bar { has @.bar is rw; method set_bar { @.bar[0] = 100;

Fwd: [perl #57656] [PROPOSAL][PIR] change PIR sugar for concat into ".." (or something else)

From: Andrew Whitworth via RT <[EMAIL PROTECTED]> Date: Thu, Aug 7, 2008 at 12:11 AM I like ".." and "~". I also like "+", if we can get IMCC to reliably understand that when used on strings it performs concatenation instead of some crazy addition. But there's a concat_p_p_p op, so

Re: [perl #57636] [TODO][PDD19] Document the reason for :unique_reg flag

From: "jerry gay" <[EMAIL PROTECTED]> Date: Thu, 7 Aug 2008 07:04:24 -0700 . . . also, if i understand satisfy patrick's use case in pge, 3) add the ability to select the register allocator used, or disable it, within a sub. a programmer who knows what he's doing should hav

Re: new article, "A Romp Through Infinity"

Supporting multiple levels of infinities, transfinite numbers or even Surreal Numbers should be considered in the same category of features as returning multiple answers from complex trig functions. They're an interesting thing to discuss and experiment with but shouldn't distract form getting

Re: [perl #57636] [TODO][PDD19] Document the reason for :unique_reg flag

On Thu, Aug 7, 2008 at 11:26 AM, Bob Rogers <[EMAIL PROTECTED]> wrote: > From: "jerry gay" <[EMAIL PROTECTED]> > Date: Thu, 7 Aug 2008 07:04:24 -0700 > > . . . > > also, if i understand satisfy patrick's use case in pge, > > 3) add the ability to select the register allocator used, or dis

Re: new article, "A Romp Through Infinity"

HaloO, Xavier Noria wrote: IMO to include something related to infinity you need to stick with some particular model and forget the rest. Well spoken. But I think that the model John has chosen is a bit too restrictive. If a type has a notion of Zero it could have a similar notion of infinity

Re: adverbs o operators

HaloO, John M. Dlugosz wrote: So do they have to go at the end of the whole expression in the current grammar? I don't follow about the spaces. The problem is term versus operator parsing. Do you write $a lt:lc $b le:lc $c I think that works and looks best. My favorite hope is that

Re: [perl #57656] [PROPOSAL][PIR] change PIR sugar for concat into ".." (or something else)

From: "Andrew Whitworth" <[EMAIL PROTECTED]> Date: Thu, 7 Aug 2008 11:36:16 -0400 On Thu, Aug 7, 2008 at 11:18 AM, Bob Rogers <[EMAIL PROTECTED]> wrote: > But there's a concat_p_p_p op, so "+" is ambiguous. In general, it > seems best to use distinct tokens for distinct operatio

Re: Reason for attributes.t fail

Jonathan Worthington wrote: Hi, Rakudo is currently failing t\spec\S12-class\attributes.t. This turns out not to be an issue with attributes, but rather exceptions. The test does: my $c = Counter.new(); try { $c.x } ok($!, 'no public accessor for private attribute'); And fails because th

Re: new article, "A Romp Through Infinity"

HaloO, [EMAIL PROTECTED] wrote: Let's just make sure we're handling inf and -inf right and leave all that other stuff until later. The point is: what is the minimum we need to be future proof and compatible to other language features. Regards, TSa. -- "The unavoidable price of reliability i

Re: Reason for attributes.t fail

On Thu, Aug 7, 2008 at 3:26 AM, Jonathan Worthington <[EMAIL PROTECTED]> wrote: > Hi, > > Rakudo is currently failing t\spec\S12-class\attributes.t. This turns out > not to be an issue with attributes, but rather exceptions. The test does: > > my $c = Counter.new(); > try { > $c.x > } > ok($!, 'n

Re: Reason for attributes.t fail

Allison Randal wrote: The Exception PMC never had a get_bool vtable function implemented, but it did previously inherit one from ResizablePMCArray. So, that test was relying on an implementation artifact. OK, then that was certainly a wart, agreed. Under what circumstances should an exceptio

Re: Reason for attributes.t fail

jerry gay wrote: seems to me this is trying to test whether there's a defined value in $!. Testing truth falls back to definedness, yes. however, you've jumped straight into blaming parrot's Exception PMC, without considering the expected perl 6 behavior. Well, I was more blaming the *chan

Re: Reason for attributes.t fail

On Thu, Aug 7, 2008 at 12:51 PM, Jonathan Worthington <[EMAIL PROTECTED]> wrote: > jerry gay wrote: >> >> seems to me this is trying to test whether there's a defined value in >> $!. > > Testing truth falls back to definedness, yes. > >> however, you've jumped straight into blaming parrot's Excepti

Re: [perl #57636] [TODO][PDD19] Document the reason for :unique_reg flag

On Thursday 07 August 2008 08:26:19 Bob Rogers wrote: > I once suggested a "null register allocator" that would do this > globally, but this is a better idea. The only use case I can think of > is debugging, particularly of the register allocator, but that's still > important. In theory, that's

Re: adverbs o operators

On Thu, Aug 07, 2008 at 06:15:07PM +0200, TSa wrote: >> Do you write >> >> $a lt:lc $b le:lc $c > > I think that works and looks best. My favorite hope is that > >$x = log:2 $y; > > flies, as well. > >$x = log:base(2) $y; > > is a bit lengthy and > >$x = log $y, :base(2); > > looks

Re: [perl #57710] Parrot segfaults after subtype type check fails

On Thursday 07 August 2008 05:16:40 Carl Mäsak wrote: > r30087: > $ ./perl6 -e 'subset A of Int where 1; my A $a = 1' # this works > $ ./perl6 -e 'subset A of Int where 1; my A $a = 0' # this fails (as > it should) but segfaults > Type check failed > [...] > Segmentation fault > > I was not able t

Re: adverbs o operators

HaloO, Larry Wall wrote: The whitespace proposal is essentially to require whitespace between any operator any following pair if the pair is intended to be a noun and not an adverb. So, then my log:base(2) would still look for the positional argument, right? Alternately, we could force eve

Re: time op inconsistent on Win32

Jonathan Worthington wrote: Hi, I've just been looking at the time op, and what it returns is somewhat platform specific. * On Win32, it's the number of seconds since January 1, 1601 If I remember correctly, some parts of Windows use 100ns ticks since 1601 to represent time. Not sure if c

Closure vs Hash Parsing

Hi, There is in the spectests this example: my $text = "abc"; my %ret; %ret = map { $_ => uc $_; }, split "", $text; is ~%ret.kv, "a A b B c C", "=> works in a map block"; However, it seems from S06: "|{...}| is always a block. However, if it is completely empty or consists of a single list,

Re: time op inconsistent on Win32

On Thu, Aug 7, 2008 at 12:40 PM, Ron Blaschke <[EMAIL PROTECTED]> wrote: > Jonathan Worthington wrote: >> >> Hi, >> >> I've just been looking at the time op, and what it returns is somewhat >> platform specific. >> >> * On Win32, it's the number of seconds since January 1, 1601 > > If I remember co

[perl #57728] [TODO] avoid 2038 bug if we haven't already.

# New Ticket Created by Will Coleda # Please include the string: [perl #57728] # in the subject line of all future correspondence about this issue. # http://rt.perl.org/rt3/Ticket/Display.html?id=57728 > Open a ticket for TODO item. -- Forwarded message -- From: jerry gay <[E

Re: time op inconsistent on Win32

Ron Blaschke wrote: Jonathan Worthington wrote: I've just been looking at the time op, and what it returns is somewhat platform specific. * On Win32, it's the number of seconds since January 1, 1601 If I remember correctly, some parts of Windows use 100ns ticks since 1601 to represent time.

Re: [perl #57636] [TODO][PDD19] Document the reason for :unique_reg flag

From: "Will Coleda" <[EMAIL PROTECTED]> Date: Thu, 7 Aug 2008 11:30:34 -0400 On Thu, Aug 7, 2008 at 11:26 AM, Bob Rogers <[EMAIL PROTECTED]> wrote: > I once suggested a "null register allocator" that would do this > globally, but this is a better idea. The only use case I can t

Re: Another adverb on operator question

On Thu, Aug 07, 2008 at 05:04:41AM -0500, John M. Dlugosz wrote: > What about adverbs on reduction operators? > > [lt :lc] $a,$b,$c # all in decreasing order I don't think that'll fly because reduce operators are parsed as single tokens to disambiguate them from array composers, and there a

Re: Another adverb on operator question

Perhaps I'm missing something; but why couldn't you say '[lt]:lc $a, $b, $c'? That is, I see the "reducing meta-operator" as a way of taking a list-associative infix operator and treating it as a function call, albeit one with a funny name. As such, you should be able to do things with a reduced

Re: Closure vs Hash Parsing

Jonathan (>): > That this means the { $_ => uc $_; } above would end up composing a Hash > object (unless the semicolon is meant to throw a spanner in the > hash-composer works?) It says you can use sub to disambiguate, but > > %ret = map sub { $_ => uc $_; }, split "", $text; > > Doesn't work sinc