You can accomplish this using some pretty basic OO patterns. You want
your client to be ignorant of the implementation of the module with
which it is talking (except to say that it will conform to a particular
interface). Also, you may want to client to be ignorant of the which
module to create
For some reason I have a problem with inheritance if the derived object
using full namespace for the base object in the ISA.
In the following, B derives from A. The directory structure is such
that A.pm lives in the same directory as B.pm
A.pm
#!/usr/local/bin/perl
package A;
sub foo
I ran into a problem using the Carp module in an INIT block while using
the XML::Parser module. It seems as though there is something
uninitialized within the module until after the INIT block. Once my
INIT block is completed, all is well. Anyone understand why using it is
problematic here?
I
There are many ways to do this. Here is just one example using a
closure.
package Remember;
# this is a closure
{
my $savedData = 0;# only accessible within this scope; side
effect is that
# it stays around as long as the module since
the following
Anyone know if you can setuid root from a perl program or module?
Jon Cassorla
--
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
