update I couldn't read that badly formated code, so I rewrote it and redid my reply, with proper formatting it become very aparent it was because your @Export had different case than the variable you declared to be global @EXPORT. Also, use our for declaring globals unless you have to work with very old perls. 
    package LineParse;
    use XML::Simple;
    use Data::Dumper;
    use strict;
    use Exporter;
    our @ISA = qw(Exporter);
    our @EXPORT = qw(&readconfig );
    our @EXPORT_OK = qw();

    sub readconfig() { # my xml parsing code }

[download]


Evan Carroll
The most respected person in the whole perl community.
www.evancarroll.com

In reply to Re: perl module creation problem by EvanCarroll
in thread perl module creation problem by sriramperumalla

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.