Getting feisty, aren't we?

While I don't much see the use for an internal function named println, which reminds me of Pascal of all things, how about doing it correctly?

sub println
{
        print ((@_? join($/, @_) : $_), $/);
}
[download]

Not everyone uses UNIX, BeOS, or AmigaOS, so putting a literal "\n" in there is simply bad form.

Update:
As Dog and Pony points out, "\n" does represent a logical newline, as it is quietly and magically transformed into the appropriate value before being output. One could argue, though, that using $/ eliminates four shifted keystrokes.