Le jeu 11/12/2003 à 16:19, Dan Anderson a écrit : > Caveat Coder! Perl can be set up so that the @INC doesn't point to the > core modules. I have seen this on shared hosting, where (I assume) the > sys admin decided to use it as a way to secure the box.
I don't get it. What would be my interest in doing that? I've already tried that with Storable.pm (I don't remember the version but I am using perl 5.6.1) and it just failed horribly because the module needed somehow to be compiled into perl libs... or something like that? I'm not really into Perl enough to get into those compilation needs, but I still have a problem, in the case of Storable.pm, because the different versions don't keep backward compatibilities. The problem I have with that is that I have different scripts which communicate from different OS and the "freezed" strings are not freezed the same way from one version to the other and my scripts can thus not communicate. I have tried to get a certain (same everywhere) module release and put it in another directory but then it wrecks from every part :-) Also, Perl 5.8.0 seems to have Storable as a core module, so it's even harder to get rid of this version. As for now, I am forced not to move to Perl 5.8.1 because of the installations already done on different client sites (pain to change it everywhere) so I "freezed" the system everywhere but I would like to find a solution. Anyway, I don't get the point of what you were saying about loading the modules from another place. Maybe the Digest::MD5 would work that way, if that's what you were meaning, but it won't work with all modules. Thx for your help (all), Yannick -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] <http://learn.perl.org/> <http://learn.perl.org/first-response>
