Re^2: File::Spew - a figment of my imagination?

File::Slurp is broken, especially with regard to character encoding and I/O layers. It should be eschewed. File::Slurper is a modern replacement, or use Path::Tiny.

The way forward always starts with a minimal test.

Comment on Re^2: File::Spew - a figment of my imagination?

Replies are listed 'Best First'.
Re^3: File::Spew - a figment of my imagination? by RichardK (Parson) on Sep 10, 2015 at 16:00 UTC
OH! Is it still broken 4+ years later?	[reply]
Re^4: File::Spew - a figment of my imagination? by dasgar (Priest) on Sep 10, 2015 at 16:36 UTC
Here's a recent blog post from Leon Timmermans (author of File::Slurper) titled "File::Slurp is broken and wrong". Personally, I have not had any issues using File::Slurp. But then again, I haven't used it in the problematic scenarios as described in the blog post and mentioned in the discussion link provided by 1nickt. Despite not encountering any issues so far, I'm thinking that I might want to revisit some of my older code to change them to not use File::Slurp to help avoid potential problems.	[reply]