"David L. Nicol" wrote:
> No, I'm not, it's the direction that RFC 61 ends up if you let it
> take you there.

You seem to be confusing:

   (1) linking C code with Perl

with

   (2) compiling Perl to C code

There is a world of difference. Swig does (1) pretty well already.
If you want a first class blessed/tied interface you learn the perl
types and internals by reading perlguts. This is *not* XS.

If you want (2) then you've got a lot of work. For example, you can't
use built-in C data types or even the C function call stack because
they aren't compatible with Perl. It's possible to design a large
library of data structures to help, but then you've simply re-invented
libperl.so. The real problems of exception handling, closures, dynamic
scoping, etc. are just not possible to solve using simple C code.

- Ken

Reply via email to