Added files:
key.c
include/parrot/key.h
t/op/key.t
Altered files:
MANIFEST
Makefile.in
include/parrot/parrot.h
core.ops
Implements generic aggregate support in the Sn registers. t/op/key.t has
quick samples of its use. It does have fairly rigorous internal tests,
but the memory all
-- Forwarded Message --
Bryan,
One possible bug-report for you - parrot-0.0.3 does not link on MacOSX
under an HFS+ filesystem due to the fact that there is a 'Parrot'
directory in the same place it is trying to link 'parrot' (HFS+ is
case-preserving but case-insensitive) - I
On Sun, Dec 09, 2001 at 07:46:46PM -0500, Bryan C. Warnock wrote:
> Proposal:
>
> For background, revisit my proposed Bytecode Format (v2) at
> http:[EMAIL PROTECTED]/msg05640.html.
> Although it is outdated, is gives a general gist of the direction of my
> thinking. In particular, pay no heed t
On Monday, December 10, 2001 10:44:09 AM Dan Sugalski wrote:
> At 02:57 PM 12/10/2001 +, Simon Cozens wrote:
>>On Sun, Dec 09, 2001 at 11:26:44PM -0500, [EMAIL PROTECTED] wrote:
>> > it has to do with the fact that the memory allocator
>> > adjusts the address before returning the chunk and f
At 08:33 AM 12/10/2001 -0500, Bryan C. Warnock wrote:
>On Monday 10 December 2001 03:06 am, Tom Hughes wrote:
> > In message <20011210011601$[EMAIL PROTECTED]>
> >
> > "Bryan C. Warnock" <[EMAIL PROTECTED]> wrote:
> > > - Endianness. The three major types are Big, Little, and Vaxian.
>
At 11:27 AM 12/8/2001 -0500, Bryan C. Warnock wrote:
>On Friday 07 December 2001 10:46 pm, Bryan C. Warnock wrote:
> > I need - er, strike that - really, really could use some absolute C type
> > abstraction (in addition to our current relative system).
> >
> > Any objections? Any objections to P
At 02:57 PM 12/10/2001 +, Simon Cozens wrote:
>On Sun, Dec 09, 2001 at 11:26:44PM -0500, [EMAIL PROTECTED] wrote:
> > it has to do with the fact that the memory allocator
> > adjusts the address before returning the chunk and free()
> > then gets confused. Does this seem to be the issue?
>
>Th
At 08:06 AM 12/8/2001 -0500, James Mastros wrote:
>On the other end of the spectrum, Microsoft nmake can't even understand ;
>within a commandline. On win9x, IIRC, it has very strange quoting
>conventions.
This has nothing to do with Make. It's a shell thing. The line gets sent
out mostly verba
On Sun, Dec 09, 2001 at 11:26:44PM -0500, [EMAIL PROTECTED] wrote:
> it has to do with the fact that the memory allocator
> adjusts the address before returning the chunk and free()
> then gets confused. Does this seem to be the issue?
That's exactly what it is! Damn, I'd been seeing this too, an
In message <20011210133529.EYKY11472.femail13.sdc1.sfba.home.com@there>
Bryan C. Warnock <[EMAIL PROTECTED]> wrote:
> On Monday 10 December 2001 03:06 am, Tom Hughes wrote:
> > In message <20011210011601$[EMAIL PROTECTED]>
> >
> > Actually VAXes have perfectly ordinary endianness - it was
On Monday 10 December 2001 03:06 am, Tom Hughes wrote:
> In message <20011210011601$[EMAIL PROTECTED]>
>
> "Bryan C. Warnock" <[EMAIL PROTECTED]> wrote:
> > - Endianness. The three major types are Big, Little, and Vaxian.
> > Supporting these three should handle the majority of cases.
>
Robert Spier <[EMAIL PROTECTED]> writes:
>There was a flurry of activity on perl6-internals a few weeks ago
>about creating/finding a cross platform build system for building
>parrot and perl6.
>
>I'm trying to restart that discussion over here in perl6-build, to try
>and get the collective minds
In message <20011210011601$[EMAIL PROTECTED]>
"Bryan C. Warnock" <[EMAIL PROTECTED]> wrote:
> - Endianness. The three major types are Big, Little, and Vaxian.
> Supporting these three should handle the majority of cases.
Actually VAXes have perfectly ordinary endianness - it was PDPs
13 matches
Mail list logo
