# from Matisse Enzer # on Friday 19 October 2007 09:21: >Finally, I am no longer sure it is such a bad thing to have non- >modules directly in @INC. I am currently undecided about this.
I don't think it is a "bad thing" across the board, but in most cases it is not a "good thing". If (and only if) it is a data file which module code needs at compile-time and there is no per-user/configurability to it, something in @INC might be a good spot for it. That is, if it is a chunk of data which you would have otherwise put in a __DATA__ section or internal variable, breaking it out into a file in @INC is ok. In your example, lookup tables for colors probably fit this. (Note that it might load faster if it were simply a Data::Dumper output, so maybe best to make it a .pm file anyway.) An image, stylesheet, or such should really go in /usr/share/foo/ or similar. A config file should really go in /etc/ or ~/.foo. See also: the freedesktop stuff. http://search.cpan.org/perldoc?File::BaseDir --Eric -- [...proprietary software is better than gpl because...] "There is value in having somebody you can write checks to, and they fix bugs." --Mike McNamara (president of a commercial software company) --------------------------------------------------- http://scratchcomputing.com ---------------------------------------------------
