Re: Questions on NCI for nasty library

2004-08-14 Thread chromatic
On Fri, 2004-08-13 at 23:47, Leopold Toetsch wrote: > Hildo Biersma <[EMAIL PROTECTED]> wrote: > > - How do I define a class with constant values that are accessible to > > other classes? > I'd just create an include file with the constants. The dot isn't > allowed in identifiers, so you would

Re: Questions on NCI for nasty library

2004-08-14 Thread Leopold Toetsch
Hildo Biersma <[EMAIL PROTECTED]> wrote: > This thread got side-track with perl5 issues, so let me ask again: > - Are there any examples of creating a PMC class that maps to a C > structure, with the PMC class (in C) setting defaults and adding > accessor methods? The UnmanagedStruct PMC all

Questions on NCI for nasty library

2004-08-13 Thread Hildo . Biersma
> "Hildo" == Hildo Biersma <[EMAIL PROTECTED]> writes: Hildo> I'm looking at writing Parrot support for a vendor library: IBM MQ Hildo> (Message Queueing, aka "MQSeries", aka "WebSphere MQ"). The current Hildo> perl module (which I maintain) uses XS code and Parrot's NCI should Hildo> simplif

Re: Questions on NCI for nasty library

2004-08-10 Thread Hildo . Biersma
> "Nick" == Nicholas Clark <[EMAIL PROTECTED]> writes: Nick> On Mon, Aug 09, 2004 at 08:53:27AM -0400, [EMAIL PROTECTED] wrote: >> - MQ has constants. Thousands of them. In the perl module, these get >> mapped to perl XS subroutines (which bloats the symbol table no >> end). For parrot, I'd

Re: Questions on NCI for nasty library

2004-08-09 Thread Dan Sugalski
At 7:17 PM +0100 8/9/04, Nicholas Clark wrote: The code is messy and needs refactoring so that it can be subclassed to generate lookup tables that return other sorts of structures, such as potentially the token lookup in the perl5 core, and the NCI signature lookup in nci.c, which is currently a li

Re: Questions on NCI for nasty library

2004-08-09 Thread Nicholas Clark
On Mon, Aug 09, 2004 at 01:18:32PM -0400, [EMAIL PROTECTED] wrote: > Not sure. I'm not lookig for advice on evolving this module for > perl5; it's gross and cumbersome, but I am not about to make deep > changes to it. I'd much rather do it right for parrot, specially > since I won't have to supp

Re: Questions on NCI for nasty library

2004-08-09 Thread Nicholas Clark
On Mon, Aug 09, 2004 at 08:53:27AM -0400, [EMAIL PROTECTED] wrote: > - MQ has constants. Thousands of them. In the perl module, these get > mapped to perl XS subroutines (which bloats the symbol table no > end). For parrot, I'd prefer to use two big hash tables of the type As in at load ti

Questions on NCI for nasty library

2004-08-09 Thread Hildo . Biersma
I'm looking at writing Parrot support for a vendor library: IBM MQ (Message Queueing, aka "MQSeries", aka "WebSphere MQ"). The current perl module (which I maintain) uses XS code and Parrot's NCI should simplify this a lot. I have two questions though: - MQ has some data structures that are a ta