Re: CGI script organisation

[dws]

But I can't figure out how to get the use operator to take a relative path (such as ../).

Use an absolute path. Something like   use lib qw(/home/LukeBoy/modules);

[LukeyBoy]

But if the module gets relocated (which it surely will when I release it) that'll mess everything up. Who knows where other users will install the stuff?

[metadoktor]

Why not create a modules subdirectory below your app so that you can do this.

use mod_dir::module1;
use mod_dir::module2;

module1->foo();
module2->foo2();

metadoktor

"The doktor is in."

[Aristotle]

I advise against that.

use mod_dir::module1;

equates to

BEGIN { require mod_dir::module1; import mod_dir::module1; }

Notice the import? That will break if the actual namespace is called module1, and not mod_dir::module1. Depending on the module, this can have a huge impact.

Makeshifts last the longest.

[LukeyBoy]

That's good too. I can use a dummy .htaccess file to block users from inadvertanly entering that directory.

[dws]

But if the module gets relocated (which it surely will when I release it) that'll mess everything up.

Then your install procedure will need to plug in a correct path.

[LukeyBoy]

Yeah, this is one way to do it. I can let the configure script process example.pl.in to example.pl to replace the paths with their actual values. It's ugly, but it'll do. Thanks!

[thraxil]

use lib qw(../some_directory);

works fine for me.

anders pearson