Re: 64-bit ints and non-capable hardware

2002-10-22 Thread Martin D Kealey
Dan Sugalski <[EMAIL PROTECTED]> wrote: > Okay, I'm about ready to just bite the bullet and declare that > INTVALs have to be 64 bit integers. > > Does anyone know of a platform that has neither native nor emulated > 64 bit integers? (One we're likely to run on, rather) I'm fairly new to Parrot

Re: [perl #18044] Assembler doesn't return a useful exit status

2002-10-22 Thread Martin D Kealey
On Mon, 21 Oct 2002, Clinton Pierce wrote: > * With bad arguments, the assembler returns 1 to the OS. Peachy. Please can we have... #include exit(EX_USAGE); // 64 on most platforms > * Upon failure, the assembler returns the status 0 to the OS and writes > some bytecode. No telling how

Re: 64-bit ints and non-capable hardware

2002-10-23 Thread Martin D Kealey
On Wed, 23 Oct 2002, Rhys Weatherley wrote: > Martin D Kealey wrote: > > [Frank Farance's paper] "specification based extended integer range" > > [at] http://wwwold.dkuug.dk/JTC1/SC22/WG14/docs/c9x/extended-integers/. > Very interesting proposal. I wish they ha

Re: Parrot bytecode reentrancy

2005-04-17 Thread Martin D Kealey
On Fri, 15 Apr 2005, Nigel Sandever wrote: > I struck me a while back that there is a contradiction in idea of a shared, > 'my' variable. > > I want to say lexical, but a var declared with 'our' is in some sense lexical. Shared-between-threads and shared-between-scopes are orthogonal properties; u

Re: parrot and refcounting semantics

2005-04-28 Thread Martin D Kealey
On Thu, 28 Apr 2005, Robin Redeker wrote: > I don't think circular references are used that much. Circular references are useful any time you need to be able to iterate over a collection, and also have to identify which collection a given object is in. This may even be implicit from other require

Re: parrot and refcounting semantics

2005-04-28 Thread Martin D Kealey
On Thu, 28 Apr 2005, Luke Palmer wrote: > Or, with the "block hooks" that I keep claiming makes timely destruction > almost never needed, it is: > > { > my $s = new CoolClass; > # ... do stuff that may throw ... > LEAVE { destroy $s } > } > > This destroys properly a

Re: About multithreading

2005-10-01 Thread Martin D Kealey
Leo wrote: > > http://www.gotw.ca/publications/concurrency-ddj.htm > > The Free Lunch Is Over: A Fundamental Turn Toward Concurrency in Software > > Herb Sutter On Tue, 20 Sep 2005, Jonathan Worthington replied: > Yup, and it's encouraging to see Perl 6 is heading in a good direction on > concurre

Re: Input / Output encoding filters.

2006-02-21 Thread Martin D Kealey
I'm a bit slow coming back to this, sorry. It seems that "seek" is used in two ways: * returning to some previously identified point (including the start or end of the file) * moving a given number of characters you want to move relative to a known location Clearly you can al

Re: [perl #40058] Disambiguate usage of class PMCs from class name lookup (pdd15, pdd06, pdd19)

2006-08-06 Thread Martin D Kealey
On Thu, 3 Aug 2006, Chip Salzenberg wrote: > KNOWN FUTURE DEVELOPMENTS > > It's already decided that we're moving class PMCs into the normal namespace > tree. This change will eliminate many uses of the class-lookup opcodes, but > not all: There's a two-level search will still be required, where t

Re: [perl #60044] [BUG?] rethrow just throwing?

2008-10-28 Thread Martin D Kealey
On Fri, 24 Oct 2008, Allison Randal wrote: > Will Coleda wrote: > > Allison Randal wrote: > > > ...you expect 'rethrow' to keep the stack trace of the original 'die'? > > Yes. > > The way to do this is to add stack trace information to the Exception's > 'stacktrace' attribute when the exception is