|( #3333=superdoc: print w/replies, xml )||Need Help??|
I see that File::Spec::VMS loads both File::Basename and VMS::Filespec - so it's at least conceivable that the bug arises from code in one of those 2 modules (the latter being more lkely than the former, I would guess).
There's a couple of if/else branches in the catfile() sub in File::Spec::VMS. I'd probably start with some debug print() statements inside that sub to determine just which route is being followed and trace it back from there ... if I had access to a VMS system: -:)
In reply to Re: File::Spec bug on VMS