Interesting point. I think I made the decision based on the name rather
than what other things do. This is a really old module that I should
probably re-think, improve, and upload into a new namespace :)
* On Fri, Oct 14 2011, sshaw via RT wrote:
Show quoted text> Fri Oct 14 18:38:29 2011: Request 71687 was acted upon.
> Transaction: Ticket created by SHAW
> Queue: Directory-Scratch
> Subject: touch(), write(), read() and their use of $, and $\
> Broken in: 0.14
> Severity: Important
> Owner: Nobody
> Requestors: SHAW@cpan.org
> Status: new
> Ticket <URL:
https://rt.cpan.org/Ticket/Display.html?id=71687 >
>
>
> The docs for touch say:
>
> Creates a file named $filename, optionally containing the elements
> of @lines separated by the output record separator "$\".
>
> But touch calls write which uses $, to separate @lines. The docs for
> write state this behavior:
>
> Each line will be ended with a "\n", or $, if it is defined.
>
> And read's docs:
>
> If you wrote the file with $, set, you’ll want to set $/ to $,
> when reading the file back in:
>
> Why is the field separator being used as the record separator?
>
> -Skye
--
print just => another => perl => hacker => if $,=$"
