Sam Tregar wrote:
>
> On Fri, 18 Aug 2000, Graham Barr wrote:
> > So it is a security issue then as it needs somewhere to cache these
> > object files, and anyone must be able to do it.
>
> The place it stores its objects is configurable, so it's only a security
> problem if you make it one! I'
On Fri, 18 Aug 2000, Graham Barr wrote:
> > No. The documentation states that the compilation is done only when the
> > source file is out of date with the companion object file. As I
> > understand it, Inline has some kind of limited automatic make ability.
>
> So it is a security issue then a
Jarkko Hietaniemi wrote:
> De ja vu. Are you familiar with Cons?
>
> http://search.cpan.org/doc/KNIGHT/cons-2.1.1/README
>
Interesting. I was not familiar with this package. I just needed a good
way to know whether a snippet of source code had been changed. Since the
snippet is probably just
Oops,
In my haste to upload version 0.23 (which supports MSWin32) I introduced
a bug which will cause "make test" to fail *only* if the user is
installing Inline.pm for the first time. Of course, everyone (except me)
caught this right away.
So I hastlily uploaded v0.24 :-) Please use that one i
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.
> (B
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:
ht
On Fri, Aug 18, 2000 at 07:20:28AM +0100, Graham Barr wrote:
> So it is a security issue then as it needs somewhere to cache these
> object files, and anyone must be able to do it.
No more insecure than having your own LIB directory, although the prospect of
every user having their own copy of ev
On Thu, Aug 17, 2000 at 05:26:18PM -0400, Sam Tregar wrote:
> On Thu, 17 Aug 2000, Nick Ing-Simmons wrote:
> > Simon Cozens <[EMAIL PROTECTED]> writes:
> > >Wow. I'm sold. Can this be how we should be doing XS in Perl 6?
> > So we now run equivalent of xsubpp and cc every time script is run?
>
>
On Thu, Aug 17, 2000 at 08:20:35PM +, Nick Ing-Simmons wrote:
> Simon Cozens <[EMAIL PROTECTED]> writes:
> >>BEGIN {$c_code = &c_code_generator()}
> >>use Inline C => $c_code; # will die if code doesn't compile
> >>myfunc1();
> >>
> >>greet('Ingy');
> >>
On Thu, 17 Aug 2000, Nick Ing-Simmons wrote:
> Simon Cozens <[EMAIL PROTECTED]> writes:
> >Wow. I'm sold. Can this be how we should be doing XS in Perl 6?
> So we now run equivalent of xsubpp and cc every time script is run?
No. The documentation states that the compilation is done only when the
On Thu, Aug 17, 2000 at 08:20:35PM +, Nick Ing-Simmons wrote:
> Simon Cozens <[EMAIL PROTECTED]> writes:
> >>BEGIN {$c_code = &c_code_generator()}
> >>use Inline C => $c_code; # will die if code doesn't compile
> >>myfunc1();
> >>
> >>greet('Ingy');
> >>
Simon Cozens <[EMAIL PROTECTED]> writes:
>>BEGIN {$c_code = &c_code_generator()}
>>use Inline C => $c_code; # will die if code doesn't compile
>>myfunc1();
>>
>>greet('Ingy');
>>greet(42);
>>
>>use Inline C => <<'END_OF_C_CODE';
>>
>>void gr
At 01:10 PM 8/17/00 +, Simon Cozens wrote:
>In comp.lang.perl.announce, Brian Ingerson wrote:
> >Inline.pm allows a programmer to write C code directly inside a Perl
> >script and just run it. No XS, no SWIG, no make. Using Inline to write
> >extension modules for the CPAN is fully supported a
In comp.lang.perl.announce, Brian Ingerson wrote:
>Inline.pm allows a programmer to write C code directly inside a Perl
>script and just run it. No XS, no SWIG, no make. Using Inline to write
>extension modules for the CPAN is fully supported and just as easy. C++,
>Fortran, Pascal, and Python are
14 matches
Mail list logo
