[log4perl-devel] Getting Log4perl working on VMS - Found some bugs?

[Ben H. <bhu...@fa...>]

Hi,

I've been using Log4perl for a while now and it seems to work fine for me, 
I just wanted to make sure all tests pass so I can distribute it to 
everyone here having to use VMS.
I realise this request might seem for a very small number of users, but I 
think one of the bugs I found is winder than just VMS



The first bug I found I think is cross-platform.  The test results were:
s4:[bhumphreys.perl.log4perl.log.t]002logger.t..........63/70
                                                              Can't open 
S4:[BHUMPHREYS.l4p-tmpfile-1433546570-140904] (no such file or d
# Looks like you planned 70 tests but ran 68.
# Looks like your test exited with 256 just after 68.

I don't know if you're familiar with VMS paths, but 
"S4:[BHUMPHREYS.l4p-tmpfile-1433546570-140904]" is a directory .

The method it uses, Log::Log4perl::Util::tmpfile_name seems to return the 
results of File::Spec::catdir.
Line 50:
    my $name = File::Spec->catdir(File::Spec->tmpdir(),
                              'l4p-tmpfile-' .
                              "$$-" .
                              int(rand(9999999)));

I've used File::Spec a bit before, and I thought to return a filename you 
need to use File::Spec->catfile(dir, filename);
I changed this to catfile instead of catdir and the tests passed.


Is this a bug? Or desired behaviour?
I would have thought this would fail on Unix too.



Other errors seem to be caused by getting the filename through the 
PatternLayout, and some File Locking issues.
I'm looking into those now.


I would really appreciate some feedback on this.


Ben