Hi Your Mother,

I've read many good things about Path::Tiny but haven't had the chance to really use it. One thing that held me back a little from switching from ::Class to ::Tiny is that Path::Class uses File::Spec internally, while Path::Tiny apparently does not (or only partially) - its doc says:

Path::Tiny does not try to work for anything except Unix-like and Win32 platforms. Even then, it might break if you try something particularly obscure or tortuous. ... All paths are forced to have Unix-style forward slashes.

So at the moment it feels a little safer and more portable to stick with Path::Class - not a particularly good reason, I know :-) So I'll definitely try out Path::Tiny when I get the chance.

Thanks,
-- Hauke D

All paths are forced to have Unix-style forward slashes.

So at the moment it feels a little safer and more portable to stick with Path::Class

Well, except for pre-OSX Macs, forward slashes should not be a problem. But File::Spec has a design problem.

Alexander

--
Today I will gladly share my knowledge and experience, for there are no sweeter words than "I told you so". ;-)