1) Instead of changing the #! line, you could have OS-specific .pl's which initialize variables to OS-specific values, the uses do to execute the common code.

2) You shouldn't need to use $sep. For that, we have core modules File::Spec and File::Basename. 

applic_linux.pl
---------------
#!/usr/bin/perl

our $logdir = "/home/ghodmode/logs";

do 'applic.pl';


applic_win32.pl
---------------
#!c:\perl\bin\perl

our $logdir = "c:\\xampp\\xampp\\webapp\\logs";

do 'applic.pl';


applic.pl
---------
use strict;
use warnings;

BEGIN {
   our $logdir;
   die(...) unless defined $logdir;
}

use File::Spec ();

my $logfile = File::Spec->catfile($logdir, 'error_log.txt');

...

[download]

Better yet would be to use a config file to hold the name of the log dir. That would be both OS-independant and more useful.

In reply to Re: Cross-Platform code by ikegami
in thread Cross-Platform code by GhodMode

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • 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! —
  • 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:
    & &amp;
    < &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.