Re^7: 'do' command is dead? Surely not?

Replies are listed 'Best First'.
Re^8: 'do' command is dead? Surely not? by Corion (Patriarch) on May 19, 2017 at 18:33 UTC
Maybe not `strict.pm` but some other (optional) module that was not present in the original system could still be loaded from `/tmp`.	[reply] [d/l] [select]
Re^9: 'do' command is dead? Surely not? by Anonymous Monk on May 19, 2017 at 18:38 UTC
the program would have to be trying to load said module first ... its expecting it to exist	[reply]
Re^10: 'do' command is dead? Surely not? by Corion (Patriarch) on May 20, 2017 at 09:31 UTC
If a module can use several optional components or, for example, uses Module::Pluggable, then a module not specified by the original author can very well be loaded. See JSON::Any, Mouse, Module::Pluggable.	[reply]
Re^11: 'do' command is dead? Surely not? by Anonymous Monk on May 25, 2017 at 00:12 UTC
Re^12: 'do' command is dead? Surely not? by Corion (Patriarch) on Jun 01, 2017 at 07:14 UTC
Re^10: 'do' command is dead? Surely not? by dsheroh (Monsignor) on May 20, 2017 at 09:12 UTC
Yes, the program does expect the module to exist. But that expectation can be incorrect. I don't know about you, but I frequently get Perl code (usually things written by coworkers...) which doesn't properly document its dependencies, resulting in attempts to load modules which aren't installed on the machine.	[reply]