On Mon, Mar 15, 2021 at 4:09 PM Nikita Popov <nikita....@gmail.com> wrote:
> On Mon, Mar 15, 2021 at 4:08 AM Sara Golemon <poll...@php.net> wrote: > >> On Sat, Mar 13, 2021 at 1:54 PM tyson andre <tysonandre...@hotmail.com> >> wrote: >> >> > >> > I've created a new RFC https://wiki.php.net/rfc/println >> > This proposes adding a global function to PHP to >> > print a string followed by a unix newline (`\n`). >> > >> > >> This isn't solving any problem that anyone is actually having. >> Yes, that includes you. You're not having this problem because it doesn't >> exist. >> >> We already have twice as many ways to output a string as any language >> needs >> and you want to add another because you'd rather type "LN" than "\N" ? >> Hard, negative ten thousand no on this. >> This is genuinely absurd. >> > > My opinion matches Sara's, though maybe I wouldn't put it quite in those > words ;) > > The difference between these two lines is one character: > > echo foo(), "\n"; > println(foo()); > > I don't think this one character is worth adding another way to output > strings, next to the two we already have (echo, print). Especially once you > take into account the not entirely unambiguous semantics of printlln(). > echo foo(), "\n" is entirely clear, and distinct from both echo foo(), > PHP_EOL and echo foo(), "<br />\n". > Apparently I am incapable of counting in the absence of a monospace font. The difference is actually two characters, but I think the point still stands... And in some cases it will actually be the other way around, because echo "foo\n"; is two characters shorter than println("foo");. Nikita
