Forum: Ruby question regarding adaption from swig/wrapper-interface from

Announcement (2017-05-07): is now read-only since I unfortunately do not have the time to support and maintain the forum any more. Please see and for other Rails- und Ruby-related community platforms.
A968e1d656cdef82cf2cfe09445548f1?d=identicon&s=25 Tammo Tjarks (Guest)
on 2007-02-07 22:45
(Received via mailing list)
actually I am fighting with the adaption of the interface to ruby. A lot
things are not the big problem.

For the start I would like to know if there is a equivalent for croak in
ruby. I used simply printf-statements in the C++-code but that is only a
poor replacement.

The other problem is much more tough. In the code the libperl++-library
been used. The code was not created by me. But if I get it properly they
create a perl-interface to C++-code and in the C++-code again a
perl-interpreter is embedded. It seems that can either start it with
attach to an existing one with

Perlinterpreter *perl;

or even request a new one with

It is somehow tricky and my problem is that I have found only very
information about libperl++.

I think also, that I have heard that only one ruby-process can be
at a time. I am not sure how the attach works in ruby.
This strange structure is especially used to for Error-handling. I do
get the full picture, but I assume they want to have the Error rised
the interpreter and not the C-code???

Sorry for the limited informations. But I haven't get the full picture
now. That is the main reason for the question :-).

Thank You,
This topic is locked and can not be replied to.