Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:104560
To: internals@lists.php.net
References: <5c7ae08d.1c69fb81.29486.402d@mx.google.com>
Message-ID: <e549d7a7-a629-d2fe-3eaa-68a419f96b7d@gmail.com>
Date: Sun, 3 Mar 2019 14:52:29 +0000
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101
 Thunderbird/60.5.1
MIME-Version: 1.0
In-Reply-To: <5c7ae08d.1c69fb81.29486.402d@mx.google.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
Content-Language: en-GB
Subject: Re: [PHP-DEV] print with newline
From: rowan.collins@gmail.com (Rowan Collins)

On 02/03/2019 19:59, Steven Penny wrote:
> 3. Add a new method, perhaps "echoln", "println", "say" or similar, 
> that outputs
>   a newline by default 


Of the suggestions put forward, this is the only one I can see having 
any chance of succeeding.

However, I think the big reason this doesn't already exist is one that's 
been touched on by other responses: PHP started as, and is still 
primarily regarded as, a language for building websites. In that 
context, newline characters are generally considered "insignificant 
whitespace"; the closest equivalent would be appending '<br>' or '<br 
/>' (depending on the dialect of HTML in use), but you're as likely to 
want "<p>$foo</p>", or "<li>$foo</li>", etc - and that's before we get 
into the tricky topic of escaping.

Even in CLI scripts, as soon as you're building anything intended for 
reuse, you're likely to write a function like log_string() which adds 
information like timestamp, category, severity. The use cases for a new 
function / keyword may therefore be rather limited.

Regards,

-- 
Rowan Collins
[IMSoP]