At 01:04 AM 8/8/00 +0000, Perl6 RFC Librarian wrote:
>=head1 TITLE
>
>Interfaces for linking C objects into perlsubs
This sounds more like we want perl to act like C's prologue code, so we can
invoke C programs without firing up a sub-process. It sounds rather nice,
but getting this working most places could be more than a little tricky. (I
can actually do it on VMS, if I can get perl built as a supervisor-mode
image, but doing it on Unix would be more... fun)
It looks like the two benefits we get are we save the time it takes to fork
and we present a little more control to the perl programmer. Is that it, in
a nutshell, or am I missing something?
Dan
--------------------------------------"it's like this"-------------------
Dan Sugalski even samurai
[EMAIL PROTECTED] have teddy bears and even
teddy bears get drunk
- RFC 61 (v2) Interfaces for linking C objects into pe Perl6 RFC Librarian
- Re: RFC 61 (v2) Interfaces for linking C objects ... Hildo Biersma
- Re: RFC 61 (v2) Interfaces for linking C obje... David L. Nicol
- Re: RFC 61 (v2) Interfaces for linking C objects ... Dan Sugalski
- Re: RFC 61 (v2) Interfaces for linking C obje... David L. Nicol
- Re: RFC 61 (v2) Interfaces for linking C ... Nick Ing-Simmons
- Re: RFC 61 (v2) Interfaces for linking C objects ... Nick Ing-Simmons
- Re: RFC 61 (v2) Interfaces for linking C obje... Dan Sugalski
- Re: RFC 61 (v2) Interfaces for linking C ... Nick Ing-Simmons
- are API definitions implementation detail... David L. Nicol
- Re: are API definitions implementatio... Dan Sugalski
- Re: are API definitions implementatio... Nick Ing-Simmons
