At 11:56 AM 11/7/2001 -1000, Tim Jenness wrote: >> not ok 28 # POSIX::errno(): 20, $!: 0 >> >> which I think means autoloading sets errno but isn't supposed to. I suspect >> it's doing a -d somewhere and leaving an errno of ENOTDIR laying about. Hmm. >> > >Well, $! is meant to be exactly errno so it seems that the magic is not >working or using POSIX::errno has set errno to something. Does it make a >difference if you define $foo after you set $errno?
Yup, defining $foo after setting $errno makes the test pass but I think defeats its purpose. I think it's supposed to verify that dynaloading has not set errno, but for us it does: $ perl -e "use POSIX; print $!;" not a directory $ perl -e "use Fcntl; print $!;" no such file or directory Note that the extensions above are sucessfully loaded; it's just that the process of dynamic loading leaves junk in errno. Prime suspects would be when it's permutating through @INC looking for the file or doing the actual dynamic loading. I'll see what I can find.
