"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
- Re: the C JIT Nathan Wiger
- we already have barewords as variables if we want them Re... David L. Nicol
- Re: we already have barewords as variables if we want the... John Porter
- Re: we already have barewords as variables if we want the... David L. Nicol
- Re: we already have barewords as variables if we want the... David L. Nicol
- Re: we already have barewords as variables if we want the... John Porter
- Re: the C JIT Sam Tregar
- Re: the C JIT David L. Nicol
- Re: the C JIT Ken Fox
- Re: the C JIT David L. Nicol
- Re: the C JIT Ken Fox
- Re: the C JIT David L. Nicol
- Re: the C JIT Uri Guttman
- Re: the C JIT John Porter
- Re: the C JIT John Porter
- Re: the C JIT John Porter
- Re: RFC 155 - Remove geometric functions from core Russ Allbery
- Re: RFC 155 - Remove geometric functions from core Nick Ing-Simmons
- Re: RFC 155 - Remove geometric functions from core Sam Tregar
- Re: RFC 155 - Remove geometric functions from core Nick Ing-Simmons
- Re: RFC 155 - Remove geometric functions from core Tom Christiansen