Ciao Mattia,
thanks for your reply. I read a bit about ABI and I guess it's
something I only want to touch with a long pole, that pole being an
extra layer of indirection I initially hoped to be able to avoid.
I like the idea of leveraging the wxPerl XS files. Any comments on why
you introduced
Hi!
> I like the idea of leveraging the wxPerl XS files. Any comments on why
> you introduced xsubppp (on top of xsubpp) for some XS files?
XS++ is much less verbose than plain XS when writing
C++ code [1], and it allows me to handle some C++ features
(like passing/returning references) without
Leopold Toetsch wrote:
> >> + #$P1 is now a array-like container PMC with three Integer elements.
> The question is of course, which type of PMC array?
The answer is surely, the array-type of the current HLL (as returned by
Parrot_get_ctx_HLL_type).
> does JSON define to deal with self-referenti
On Oct 23, 2005, at 6:44 PM, Leopold Toetsch wrote:
On Oct 21, 2005, at 18:07, Will Coleda wrote:
There is now rudimentary support for converting parrot objects to
JSON strings.
+ # generate a JSON representation of a PMC.
+ $S0 = _json( $P0 )
$P0 = new .Array
$P0[0] = $P0
et
On Wed, Oct 19, 2005 at 09:59:15PM +0100, Nicholas Clark wrote:
> I think the better solution is going to be to keep them in src/extend.c,
> and auto-generate a second file for the vtable calls. So the version attached
> generates src/extend_vtable.c
I like that separation.
> chromatic:
> > I thi
A question recently arose (about extend.c) about when it's OK to
change a public API, or remove it as obsolete.
Mostly I want to avoid surprise breakages. Not that I can eliminate
them. (I suspect I'll be responsible for a good number of them. New
lexical subsystem, anyone?) But for smaller th
Hi Nick,
I've added a src test that shows iteration through a hash from C
(t/src/hash.t #10) and disabled capturing SIGHUP, as mentioned on
#parrotsketch.
The other TODO [1] will take a bit of time. Currently the hash buckets
are filled from right to left, which makes iteration not stable, w
> [leo - So 23. Okt 2005, 12:25:29]:
> > As Parrot_setup_args() is so far only used for passing 'output' to the
> > exec runcore, I propose a quick fix.
> >
> > i. Do not use STRING register for passing options
> > ii. Move interp->imc_info->output to interp->output_file and use
> > interp->outpu
The subroutine check_progs defined in lib/Parrot/Configure/Step.pm is not
portable (doesn't work on MSWin32).
On MSWin32, the real filename of a program is prog.exe, prog.com, prog.bat
or prog.cmd , so if -x 'prog' is not enough.
This subroutine is currently used by config/inter/lex.pl & yacc
