Re: wxWindows Support / Interfacing libraries with Parrot

2003-07-10 Thread Tupshin Harper
Benjamin Goldberg wrote: Leopold Toetsch wrote: Tupshin Harper wrote: I'm not a "GCC person", but I do have an interest in this working. I did some exploratory work (mostly getting familiar with the GCC backend mechanism and with PASM), and quickly ran into what appeared to be fundamental

Re: wxWindows Support / Interfacing libraries with Parrot

2003-07-10 Thread Benjamin Goldberg
Leopold Toetsch wrote: > > Tupshin Harper wrote: > > > > > I'm not a "GCC person", but I do have an interest in this working. I > > did some exploratory work (mostly getting familiar with the GCC > > backend mechanism and with PASM), and quickly ran into what appeared > > to be fundamental roadbl

Re: wxWindows Support / Interfacing libraries with Parrot

2003-07-10 Thread Tupshin Harper
Leopold Toetsch wrote: Tupshin Harper wrote: I'm not a "GCC person", but I do have an interest in this working. I did some exploratory work (mostly getting familiar with the GCC backend mechanism and with PASM), and quickly ran into what appeared to be fundamental roadblocks regarding gcc's pr

Re: wxWindows Support / Interfacing libraries with Parrot

2003-07-09 Thread Leopold Toetsch
Tupshin Harper wrote: I'm not a "GCC person", but I do have an interest in this working. I did some exploratory work (mostly getting familiar with the GCC backend mechanism and with PASM), and quickly ran into what appeared to be fundamental roadblocks regarding gcc's predilection for generatin

Re: wxWindows Support / Interfacing libraries with Parrot

2003-07-09 Thread Tupshin Harper
Leopold Toetsch wrote: Why the smilies ;-) Parrot is a fine processor well suited for an optimizing compiler and with a reasonable architecture. Its not the first time that I'm thinking of such a hack. ... though it would need some extensions at both sides. Are some gcc people listening? leo I

Re: wxWindows Support / Interfacing libraries with Parrot

2003-07-07 Thread Leopold Toetsch
Christian Renz wrote: The easiest way isn't avaialble yet. That is custom dynamically loaded PMCs (classes) representing some functionality. Hmm... then I think I misunderstood something. I thought PMCs are only used for language-specific data types (e.g. "PerlScalar", I thought of wxWindows data

Re: wxWindows Support / Interfacing libraries with Parrot

2003-07-06 Thread Christian Renz
The easiest way isn't avaialble yet. That is custom dynamically loaded PMCs (classes) representing some functionality. Hmm... then I think I misunderstood something. I thought PMCs are only used for language-specific data types (e.g. "PerlScalar", "PythonString") that are part of the Parrot core a

Re: wxWindows Support / Interfacing libraries with Parrot

2003-07-04 Thread Leopold Toetsch
Christian Renz wrote: What is the easiest way to make a monster like wxWindows (in terms of classes) available for Parrot? The easiest way isn't avaialble yet. That is custom dynamically loaded PMCs (classes) representing some functionality. Alreay working is the NCI (Native call interface) to

Re: wxWindows Support / Interfacing libraries with Parrot

2003-07-04 Thread Christian Renz
GUI toolkit for Parrot -- TIMTOWTDI -- but it sure would be sweet to have, and definitely would not hurt Parrot-based application Whoops. Just to clarify: It would be sweet to have an interface for wxWindows in Parrot -- not the official endorsement. And let me try to formulate a nice and clear que

wxWindows Support / Interfacing libraries with Parrot

2003-07-04 Thread Christian Renz
Actually, I was the one mentioning it in a completely offhand remark in some discussion about the future of wxWindows ;-). I'm not looking for official endorsement of wxWindows as "the" GUI toolkit for Parrot -- TIMTOWTDI -- but it sure would be sweet to have, and definitely would not hurt Parrot-b