On Sep 7, 3:59 pm, e...@libero.it wrote:
[ snip ]
> ...creates projects of "perl nature"
> with a particular path: I must modify the perl build path but I don't
> know what I have to do...
[ snip ]
> a module (file.pm, is a mine particular
> module who requires a particular path because call different USE in
> his package) that is loaded at the same time of the perl project
> returns errors because of some USE in file.pm .... who are not able to
> find the right path
>
> My java code now is:
[ snip java ]
I don't know anything about Eclipse or Java, but as far as Perl is
concerned, you could read about "@INC" in "perldoc perlvar":
=======================
@INC
The array @INC contains the list of places that the do EXPR, require,
or use constructs look for their library files. It initially consists
of the arguments to any -I command-line switches, followed by the
default Perl library, probably /usr/local/lib/perl, followed by ``.'',
to represent the current directory. (``.'' will not be appended if
taint checks are enabled, either by -T or by -t.) If you need to
modify this at runtime, you should use the use lib pragma to get the
machine-dependent library properly loaded also:
use lib '/mypath/libdir/';
use SomeMod;
You can also insert hooks into the file inclusion system by putting
Perl code directly into @INC. Those hooks may be subroutine
references, array references or blessed objects. See require in the
perlfunc manpage for details.
=======================
--
Klaus
|