d from CVS about 12 hours ago and was rebuilt from realclean.
Thanks,
Steve Gunnell
*sigh*
Please don't apply this patch ... It causes the most recent svn tree to
segfault when trying to build PGE:
gmake[1]: Leaving directory `/home/steveg/parrot/src/dynclasses'
gmake -C compilers/pge
gmake[1]: Entering directory `/home/steveg/parrot/compilers/pge'
../../parrot mklib.pir >PGE/Li
The errors reported by valgrind have also gone in the latest SVN
release. This now seems to be a non-issue. 8-)
Struct PMC?
When using the Read/Readline opcodes how do we specify what encoding is
to be assumed for the incoming string?
Thanks and Merry Christmas,
Steve Gunnell
On Mon, 2005-12-26 at 00:40 +0100, Leopold Toetsch wrote:
> On Dec 25, 2005, at 23:48, Steve Gunnell wrote:
[snip]
>
> > When using the Read/Readline opcodes how do we specify what encoding is
> > to be assumed for the incoming string?
>
> There is one output e
to me that with coroutines and threads you might have
diverging contexts with different active exceptions and actions. So is a
stack the correct model for this or are we talking a hierarchical chain
of contexts each with a stack. Sort of like the user stack I guess.
Cheers,
Steve Gunnell
On Sat
On Sun, 2006-01-08 at 11:05 -0500, Bob Rogers wrote:
>From: Steve Gunnell <[EMAIL PROTECTED]>
>Date: Sun, 08 Jan 2006 15:02:37 +0800
>
>Hi,
>
>I'm sitting here thinking about cross language calls and what I
don't
>see anywhere is a
open "foo"
push $P0, 'ebcdic'
push $P0, 'ascii'
For mainframes.
$P0 = open "foo"
push $P0, 'encrypt_blowfish'
push $P0, 'adaptive_huffman'
push $P0, 'escaped_ascii'
push $P0, 'utf8'
You can figure it out
Cheers,
Steve Gunnell
