Greets,
It appears that once a module gets installed in strict accordance
with the "Writing Modules with Inline" guidelines, UNTAINT becomes
unnecessary, since Inline only gives itself permission, so to speak,
to look in a single directory for the compiled files, and that
directory is not derived from a tainted variable.
The relevant section of the Inline POD is...
[begin excerpt]
The important things to note here are that you must specify a NAME
and VERSION parameter. The NAME must match your module's package
name. The VERSION parameter must match your module's $VERSION
variable and they must be of the form /^\d\.\d\d$/.
NOTE: These are Inline's sanity checks to make sure you know what
you're doing before uploading your code to CPAN. They insure that
once the module has been installed on someone's system, the module
would not get automatically recompiled for any reason. This makes
Inline based modules work in exactly the same manner as XS based ones.
[end excerpt]
However, during development, it is necessary to specify DIRECTORY if
you want to run with -T enabled.
Thanks to all for the help.
Marvin Humphrey
Rectangular Research
http://www.rectangular.com/
