\n is not magically mapped to $/ "behind the scenes". There are so many misconceptions combined in that sentence that I'm at a loss at where to start.

My reaction is strong because these many misconceptions are common, I've railed against them several times, and I respect you enough to be truely shocked to hear this from you.

It's late and I'm very tired and yet also rather busy so I'll make the rude suggestion that you might want to super search for nodes by me regarding newline + $/ + \n + \r (not because I'm the only one who has anything useful to say on that subject, but because even using all of those terms, I suspect you'd otherwise get a lot to sort through while I'm sure I have several treatments of these all-too-common misconceptions under my name).

Update: Struck out one search term to yield a more interesting search. Though the meat of it is mostly collected in Re^4: Line Feeds (rumor control).

Ah, I was missing the last paragraph from the linked node. There is some magic mapping – I remember that much because I started learning Perl on Windows; but it happens elsewhere than what I thought – which I never found out first-hand because I left Windows behind at a time when I was still a Perl greenhorn.

Thanks for the correction. (And yes, I know the issue is touchy. :-))

I was going to ask a question to be sure whether I understood correctly, then I remembered binmode… and now it’s all coming back. Maybe I wasn’t so green back then; maybe it has simply been too long.

At least, if my regained understanding is right, my advice is sound anyway: that in general, you want to use \n and not worry about it; and that if you have files from other platforms, you’ll have to convert anyway.

Makeshifts last the longest.