On Thu, 17 Aug 2000, Mikael Claesson wrote:
> I plan to keep all lowerlevel database stuff in C, and
> embed it in a perl module. Will this make things run
> slower than if I made it all in perl?
It shouldn't. Keep in mind though, when you use DBI from perl you are
still doing all the low-level
On Thu, 17 Aug 2000, Barrie Slaymaker wrote:
> Mikael Claesson wrote:
> >
> > with mod_perl it looks even better.
>
> Cool. Welcome.
>
> > I plan to keep all lowerlevel database stuff in C, and
> > embed it in a perl module. Will this make things run
> > slower than if I made it all in perl?
Mikael Claesson wrote:
>
> with mod_perl it looks even better.
Cool. Welcome.
> I plan to keep all lowerlevel database stuff in C, and
> embed it in a perl module. Will this make things run
> slower than if I made it all in perl?
Usually faster, but whether that's significant in your applicat
I've always done all my serious cgi-programming in C,
but now I've been forced to lern perl and I kinda
figure it's not that bad. And with mod_perl it looks
even better.
I plan to keep all lowerlevel database stuff in C, and
embed it in a perl module. Will this make things run
slower than if I ma
# Library: /path/to/library/foo.pm
use lib 'path/to/library';
use foo;
Make sure that the process has permissions to read the file too.
Dana
On Sun, 09 Jul 2000, Srinidhi Rao S wrote:
>
> Hi all,
> I have a small problem. I have a package which is not situated in perl\lib folder.
>It has a
Hi all,
I have a small
problem. I have a package which is not situated in perl\lib folder. It has a
different path. I have some problems in copying this to library folder. Can I
use the package from the present position without copying to the library
folder?? How do tell the perl compiler
