Re: wxParrot -- linking problems

2005-10-24 Thread Mattia Barbon \<[EMAIL PROTECTED]>
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

Re: wxParrot -- linking problems

2005-10-24 Thread Christian Renz
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

Re: wxParrot -- linking problems

2005-10-22 Thread Roger Browne
Mattia Barbon wrote: > ... or you might use > the C++-to-C bindings that have been created for wx.NET and/or wxEiffel. wxEiffel can be accessed from here: http://eiffelzone.com/esd/wxeiffel/index.html It hasn't been maintained for a few years, but the C bindings might still be a useful basis for

Re: wxParrot -- linking problems

2005-10-22 Thread Mattia Barbon
On Sat, 22 Oct 2005 09:33:50 +0200 Christian Renz <[EMAIL PROTECTED]> wrote: Hello, > How do I find the right symbol name for a function? For example, the > void wxBell(void) function can be found in the library as __Z6wxBellv > (found using otool -vT /usr/lib/libwx.dylib), but I guess on Wind

wxParrot -- linking problems

2005-10-22 Thread Christian Renz
Hi all, I've recently decided to try to hook up the wxWidgets GUI library with parrot and Pugs. I haven't dabbled much with parrot yet so I consider this a good way to learn more :-). Right at the start, I ran into a curious problem loading the Wx libraries with loadlib. (I'm on Mac OS X 10.4, b