cheers mates,
i have a quite huge perl script which includes a lot of modules, though some
of them might not be used at all depending on the user's interaction. so it
takes some time for the script until the compiler finishs its work an i
thought about possibilities to improve the startup speed. i found this
autouse modul which looks like something suitable, as per the documentation
this feature should postphone the compilation of a module from the startup
of the script to the stage where it is really used, correct ??? ok, here's a
snippet from which i expect that it should use Getopt::Long first when the
function GetOptions is used and takes care of the Win32::OLE module first
when the object is created
use autouse 'Getopt::Long' => qw(GetOptions);
use autouse 'Win32::OLE' => qw(new);
(...)
GetOptions ('h', \$bla);
(...)
print "Initialising MS-Excel OLE object ... ";
($Ex=Win32::OLE->new('Excel.Application')) ? (print "OK\n") : (die $!);
my $Book=$Ex->Workbooks->Open("$ENV{TEMP}\\tafel.xls") || warn $!;
$Ex->Quit;
----- it works for GetOptions, but since 'new' is not really a function, the
system doesn't seem to autoload Win32::OLE, thus terminating the script at
this stage ....
Initialising MS-Excel OLE object ... Can't locate object method "new" via
packag
e "Win32::OLE" at tk.pl line 7.
any idea? or is there a possibility to use a kind of 'dummy' function, with
the help of which i can tell the system "now it's time to load this module".
or have i misunderstood 'autouse' completely?
TIA
till
---
You are currently subscribed to perl-win32-users as: [archive@jab.org]
To unsubscribe, forward this message to
[EMAIL PROTECTED]
For non-automated Mailing List support, send email to
[EMAIL PROTECTED]
