check your platform somehow, and make modules for each that expose a common interface,
so you can pull one out and drop in the other with a minimum of fuss.
you could then eval{} the correct one, or put them in separate files and do() the
filename. both of these are somewhat similar to the use keyword, and in your
circumstance provide pretty much what you're looking for.
if both expose the same methods, you now have a fork() call that works transparently
under solaris and win32.
On Tue, 6 Jul 2004 13:35:49 -0700, Carter Thompson <[EMAIL PROTECTED]> wrote:
I have a script that is utilized on both Solaris and Windows.
In the Solaris environment I use fork() to create a separate
process, in the Windows environment I use Win32::Process. This
unfortunately creates a bit of a problem when I attempt to
run the script on Solaris since the compiler attempts to find
the Win32 modules I've "used". What's the easiest way to
implement this? I've already checked into autouse and require.
Thanks!
Carter.
_______________________________________________
Perl-Win32-Users mailing list
[EMAIL PROTECTED]
To unsubscribe: http://listserv.ActiveState.com/mailman/mysubs
_______________________________________________
Perl-Win32-Users mailing list
[EMAIL PROTECTED]
To unsubscribe: http://listserv.ActiveState.com/mailman/mysubs
