What?

Inline::CPP writes xs modules for you , so you can call cpp functions from external cpp libraries without learning much xs

It comes with "tutorial"

RPerl converts Perl 5 source code into C++ source code

RPerl then converts the c++ code it created from perl 5 source code, into xs module, using Inline::CPP

There is no tutorial for explaining the RPerl way of wrapping an external library , ...GMPInteger_cpp.pm is as close to an example as you will find

...GMPInteger_cpp.pm is RPerl specific way of using Inline::CPP to call cpp functions from external cpp libraries ...

Will_the_Chill has been here in a while

Open an issue at https://github.com/wbraswell/rperl/issues and maybe negotiate :)

If rperl is just a layer on top of Inline::CPP, then what is the advantage over patching B::Deparse to convert Perl Snippets to CPP?

For instance code like the following

sub func :cpp int {
  my int ($a,$b) = @_;
  return $a+$b
}
[download]

is (after predefining :cpp and int) legal perl5 syntax and B::Deparse gets all necessary details.

sub func {
    (my int ($a, $b)) = @_;
    return $a + $b;
}
use attributes ('main', sub {
    (my int ($a, $b)) = @_;
    return $a + $b;
}
, 'cpp', 'int');
[download]

So whats the extra value of rperl?

Cheers Rolf
_{(addicted to the Perl Programming Language :)
Wikisyntax for the Monastery FootballPerl is like chess, only without the dice}

If rperl is just a layer on top of Inline::CPP, then what is the advantage over patching B::Deparse to convert Perl Snippets to CPP? ...So whats the extra value of rperl?

You tell me?

Is it not clear? I mean you must have at this point read everything there is to read about RPerl, the faq , docs , benchmarks / examples , jokes / original discussions about creating rperl...

Old clues https://metacpan.org/source/RURBAN/B-C-1.57/ramblings/rperl.md

Open an issue at https://github.com/wbraswell/rperl/issues and maybe negotiate :)

Done! https://github.com/wbraswell/rperl/issues/105