Move @var_arr up and put parenthesis around the list of exported variables to toss it in a more explicit list context. It's a good idea to put your variables in @EXPORT_OK first, because someday you'll see the light and want to only export those variables that your program asks for. :) 
package my_global;
require Exporter;

my @var_arr = qw( $var4 $var5 $var6 );

our $VERSION = 1.00;
our @ISA       = qw(Exporter);
our @EXPORT_OK = (@var_arr, qw( $var1 $var2 $var3 ));
our @EXPORT    = @EXPORT_OK;

# Just to test...
$var1 = "hi";
$var4 = "bye";
1;

[download]
And the test code: 
use strict;
use my_global;  #or <B>use my_global qw($var1 $var4);</B>

print "var1: $var1\n";
print "var4: $var4\n";
exit;

[download]

In reply to Re: @Export Quickie by joealba
in thread @Export Quickie by Eradicatore

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.