Re: Config::Tiny croaks at runtime, not in debugger

Thanks hawkex, and sorry for the delay (I wasn't at the office these days)

Apparently the problem is automagically fixed by downloading the CGIs to the FreeBSD destination host. It works as expected.

Probably I should blame Apple's implementation of Apache and/or CGI, since my dev server is MacOSX.

Cheers,

Xav

Comment on Re: Config::Tiny croaks at runtime, not in debugger

Replies are listed 'Best First'.
Re^2: Config::Tiny croaks at runtime, not in debugger by Your Mother (Archbishop) on May 17, 2016 at 17:45 UTC
I really recommend reading haukex's post again and taking his advice to heart. Besides security concerns, changing directories in code is, to me, code smell. Lots of Perl devs, including me, work on OS X and it doesn't seem to have any more gotchas than any other nix. And like any other nix, I highly recommend against tampering with the System perl. That includes installing new modules. Plain Perl will likely be fine but once you mess with the wrong C-based module/lib, you may hose your entire installation. perlbrew and local::lib are a couple of ways to make it easier to have it all.	[reply]

Replies are listed 'Best First'.

Re^2: Config::Tiny croaks at runtime, not in debugger
by Your Mother (Archbishop) on May 17, 2016 at 17:45 UTC

I really recommend reading haukex's post again and taking his advice to heart. Besides security concerns, changing directories in code is, to me, code smell. Lots of Perl devs, including me, work on OS X and it doesn't seem to have any more gotchas than any other *nix. And like any other *nix, I highly recommend against tampering with the System perl. That includes installing new modules. Plain Perl will likely be fine but once you mess with the wrong C-based module/lib, you may hose your entire installation. perlbrew and local::lib are a couple of ways to make it easier to have it all.

[reply]