<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
<meta name="Generator" content="Microsoft Exchange Server">
<!-- converted from text --><style><!-- .EmailQuote { margin-left: 1pt; padding-left: 4pt; border-left: #800000 2px solid; } --></style>
</head>
<body>
<meta content="text/html; charset=UTF-8">
<style type="text/css" style="">
<!--
p
{margin-top:0;
margin-bottom:0}
-->
</style>
<div dir="ltr">
<div id="x_divtagdefaultwrapper" dir="ltr" style="font-size:12pt; color:#000000; font-family:Calibri,Helvetica,sans-serif">
<p>Hi Stef,</p>
<p><br>
</p>
<p>that's a strawman, I only talked about linebreaks, not about paragraphs. :-) We definitely should not merge all paragraphs automatically. The same applies to indentation. But precisely to make these elements visible, I think it is important that we do not
intermix line breaks (for text composition) with paragraphs (semantic units)! We already have too many comments in the image where I often wonder "is this a new thought or did the author just try to keep the lines short?".</p>
<p><br>
</p>
<p>I hope you will agree that the following two texts are semantically identical? Then they should not be encoded differently in the source code of a method:</p>
<p><br>
</p>
<p><img size="26000" id="x_img455689" tabindex="0" style="max-width:99.9%" src="cid:9866d517-72b6-4288-9a60-4d1e3f83a129"><br>
</p>
<p><br>
</p>
<p>Best,</p>
<p>Christoph</p>
</div>
<hr tabindex="-1" style="display:inline-block; width:98%">
<div id="x_divRplyFwdMsg" dir="ltr"><font face="Calibri, sans-serif" color="#000000" style="font-size:11pt"><b>Von:</b> Squeak-dev <squeak-dev-bounces@lists.squeakfoundation.org> im Auftrag von Stéphane Rollandin <lecteur@zogotounga.net><br>
<b>Gesendet:</b> Montag, 4. April 2022 16:43:57<br>
<b>An:</b> squeak-dev@lists.squeakfoundation.org<br>
<b>Betreff:</b> Re: [squeak-dev] Manual line breaks in code</font>
<div> </div>
</div>
</div>
<font size="2"><span style="font-size:10pt;">
<div class="PlainText">> I feel reminded of some recent discussions about pretty-printing. Some
<br>
> people apparently want to control every detail of the appearance of <br>
> their source code (line-breaking, text composition etc.),<br>
<br>
I would be one of these people, but I would say it otherwise:<br>
<br>
when I layout my code, and my comments, I am writing for another human <br>
being (most probably myself in the future). And when I read source code, <br>
and comments therein, I read what another human being has written.<br>
<br>
Indentation, line breaks, etc all convey some meaning (otherwise we <br>
would not even bother about formatting in the first place).<br>
<br>
To assume that an algorithm can properly "pretty-print" a hunman output <br>
intended to another human, we must assume that nothing is lost in the <br>
process.<br>
<br>
Now if "details" did not matter, I could have said:<br>
<br>
I would be one of these people, but I would say it otherwise: when I <br>
layout my code, and my comments, I am writing for another human being <br>
(most probably myself in the future). And when I read source code, and <br>
comments therein, I read what another human being has written. <br>
Indentation, line breaks, etc all convey some meaning (otherwise we <br>
would not even bother about formatting in the first place). To assume <br>
that an algorithm can properly "pretty-print" a hunman output intended <br>
to another human, we must assume that nothing is lost in the process. Or <br>
maybe I could have said:<br>
I would be one of these people,<br>
but I would say it otherwise:<br>
when I layout my code,<br>
and my comments,<br>
I am writing for another human being<br>
(most probably myself in the future).<br>
And when I read source code,<br>
and comments therein,<br>
I read what another human being has written.<br>
Indentation,<br>
line breaks,<br>
etc all convey some meaning<br>
(otherwise we would not even bother about formatting in the first place).<br>
To assume that an algorithm can properly "pretty-print" a hunman output <br>
intended to another human,<br>
we must assume that nothing is lost in the process.<br>
<br>
But to me, these details matter.<br>
<br>
Stef<br>
<br>
</div>
</span></font>
</body>
</html>