On Thu, Aug 17, 2000 at 07:01:59PM -0700, Brian Ingerson wrote:
> Hi all,
>
> This is Brian Ingerson (the Inline.pm author). My coworker, Colin Meyer,
> tipped me off to this thread. I thought I'd throw in a few tidbits to
> make sure everyone's on track. But first of all, make sure to RTFM.
> (Because I put a lot of effort in explaining it there) The latest copy
> is:
>
> http://search.cpan.org/doc/INGY/Inline-0.23/Inline.pod
>
> Inline.pm is meant to be a reasonable alternative to XS. I thought of
> the idea at the Conference, after one of Damian's Parse::RecDescent
> talks. It is this module (and Digest::MD5) that make it possible.
>
> As some of you have figured out, Inline takes a C source code string (or
> file or snippet...) as an argument to a 'use' statement. An MD5 digest
> fingerprint is taken of that source code and used to produce a unique
> shared object name, such as:
>
> main_C_example001_pl_3a9a7ba88a8fb10714be625de5e701f1.so
>
> Then that module is searched for in one of several possible places
> starting with the INSTALLSITEARCH directory of @INC. If it isn't found
> then a build area is generated, a build performed, and the result is
> DynaLoaded for immediate execution. The next time the script or module
> is run, the shared object will already exist, and the code will just
> run. If the C source is modified, the fingerprint will change, and the
> object gets recompiled. Viola.
De ja vu. Are you familiar with Cons?
http://search.cpan.org/doc/KNIGHT/cons-2.1.1/README
--
$jhi++; # http://www.iki.fi/jhi/
# There is this special biologist word we use for 'stable'.
# It is 'dead'. -- Jack Cohen
