One way would be to keep in mind that the use lib pragma adds an architecture-dependant directory below the directory you name. So you could place the version for Win under the "whatever windows is" subdirectory, and the other version under the other directory.

Another would be to have a wrapper interface that does something like:

BEGIN {
  eval 'require Win32::Internet';
  unless ($@) {
    require MyWin32Wrapper;
    MyWin32Wrapper::->import();
  } else {
    require Net::FTP;
    # Net::FTP::->import(); # OO interface - no need to do this
    require MyUnixWrapper;
    MyUnixWrapper::->import();
  }
}
[download]

and then set up a common interface defined two different ways, depending on the success of requiring the Win32 version. So both of your wrapper files would define and export, say, fetch_file, but in different ways.

-- Randal L. Schwartz, Perl hacker

---

---

Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!

Titles consisting of a single word are discouraged, and in most cases are disallowed outright.

Read Where should I post X? if you're not absolutely sure you're posting in the right place.

Please read these before you post! —

• How do I compose an effective node title?
• How do I post a question effectively?
• Markup in the Monastery

Posts may use any of the Perl Monks Approved HTML tags:

a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr

You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)

	For:		Use:
	&		&
	<		&lt;
	>		&gt;
	[		&#91;
	]		&#93;

Link using PerlMonks shortcuts! What shortcuts can I use for linking?

See Writeup Formatting Tips and other pages linked from there for more info.