Re: Re: Re: CGI script organisation

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();
[download]

metadoktor

"The doktor is in."

Comment on Re: Re: Re: CGI script organisation Download Code

Replies are listed 'Best First'.
Re^4: CGI script organisation by Aristotle (Chancellor) on Jan 27, 2002 at 21:19 UTC
I advise against that. `use mod_dir::module1;` [download] equates to `BEGIN { require mod_dir::module1; import mod_dir::module1; }` [download] 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.	[reply] [d/l] [select]
Re: Re: Re: Re: CGI script organisation by LukeyBoy (Friar) on Jan 27, 2002 at 10:59 UTC
That's good too. I can use a dummy .htaccess file to block users from inadvertanly entering that directory.	[reply]