Apart from use and require it as also possible to do a file. On the file include spectrum, do would be the rawest method, and use would be the most refined.

It should be noted in passing that #include as a concept doesn't really pan out in Perl. Yes, you can embed perl code in external files, but then you must ensure that the code is run a perfectly trusted environment, otherwise Really Bad Shi^WThings can happen. That is, even if a user cannot modify your code, if they can edit a config file that is Perl code waiting to be eval'ed, then you are wide open in terms of security vulnerabilities.

A better approach is to use configuration files to store data, and parse it all. There are a number of modules that make this simple to do. For instance, if you are familiar with Win32-style .ini files, there is a module to do that, and a few more besides.

In any event, you should also read perlsec and tainting, to be make sure that people don't try and make your program do naughty things, like rm -rf /.

--

g r i n d e r
just another bofh

print@_{sort keys %_},$/if%_=split//,'= & *a?b:e\f/h^h!j+n,o@o;r$s-t%t#u';