I haven't used Inline::CPP or Inline::C for that matter.

Yes it can handle complex classes and data types.

What you are attempting to do is remotely possible, but it depends on what it is.

Asides from compiling this stuff and what not, you have to provide typemaps and wrapper functions to your legacy api, so you can access it from perl. This requires wrapping/translating perl data structures, into whatever your API takes.

I haven't done any of this, but you can find examples on the site.

Don't I sound convincing? ;)

Here's an example: Image::Filter::Blur draft

____________________________________________________
** The Third rule of perl club is a statement of fact: pod is sexy.

In reply to Re: legacy C++ code, SOAP::Lite and Inline::CPP by PodMaster
in thread legacy C++ code, SOAP::Lite and Inline::CPP by rbc

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.