<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
<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>Not for neither against that change. I use the Transcript very rarely only - unless you are dealing with processing issues, variable assignments and #inspect/#explore/#halt[Once] have felt more "live" and direct to me. Others shall decide about that proposal.
:-)</p>
<p><br>
</p>
<p>Just one thought: Currently, our tools display a flag for every method that contains Transcript, halt, flag, needsAttention, or a few others. If we establish #transcriptShow etc., we should make sure to add this selector to this list. Analogously, when you
file out a changeset, it needs to detect these selector for the slip detection.</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 mail@jaromir.net <mail@jaromir.net><br>
<b>Gesendet:</b> Montag, 6. Dezember 2021 21:25:40<br>
<b>An:</b> squeak-dev@lists.squeakfoundation.org; das.linux@gmx.de<br>
<b>Betreff:</b> Re: [squeak-dev] Syntactic sugar for Transcript show:</font>
<div> </div>
</div>
</div>
<font size="2"><span style="font-size:10pt;">
<div class="PlainText">Hi Tobias,<br>
<br>
I can't believe I copied the wrong example - indeed I meant<br>
<br>
Object>>transcriptShowln<br>
<br>
Transcript showln: self<br>
<br>
Anyway, I hear your objection and understand it's by no means "important"; it just seemed to me (1) convenient and (2) as a beginner I struggled with the Transcript concept - so it might serve as a little help to future beginners, to hide Transcript at least
for a moment before they get used to it :)<br>
<br>
Thanks for your time,<br>
<br>
~~~<br>
^[^ Jaromir<br>
<br>
Sent from Squeak Inbox Talk<br>
<br>
On 2021-12-06T21:19:51+01:00, das.linux@gmx.de wrote:<br>
<br>
> Hi Jaromir<br>
> <br>
> <br>
> > On 6. Dec 2021, at 20:16, mail at jaromir.net wrote:<br>
> > <br>
> > Hi all,<br>
> > <br>
> > I'd like to propose two little unary helper methods to facilitate printing to the Transcript window. It would allow<br>
> > <br>
> > #(1 2 3) transcriptShowln<br>
> > <br>
> > in addition to<br>
> > <br>
> > Transcript cr; show: #(1 2 3)<br>
> > <br>
> > You could sprinkle such calls into existing code without having to change too much punctuation (like statements or parentheses etc.) just like calling #inspect or #explore.<br>
> > <br>
> > Similar implementation is present in Cuis or Pharo and a simple "print" command is usual in most languages (except a few like Java).<br>
> > <br>
> > As for naming: I incline towards using the verb show rather than print because Transcript print: doesn't show the output until you flush it while Transcript show: displays the output immediately. Adding 'transcript' to the name allows for easy spotting
of these calls in the code; plain #print or #show could collide with namesake methods.<br>
> > <br>
> > Object>>transcriptShowln<br>
> > <br>
> > Transcript cr; show: self<br>
> > <br>
> > <br>
> > Object>>transcriptShow<br>
> > <br>
> > Transcript show: self<br>
> > <br>
> > If there are no objections I'll send a changeset to the Inbox.<br>
> <br>
> I think <br>
> <br>
> Transcript showln: anObject <br>
> <br>
> is sufficient.<br>
> <br>
> If not, you always have Object>>printOn:<br>
> <br>
> Best regards<br>
> -Tobias<br>
> <br>
> <br>
<br>
</div>
</span></font>
</body>
</html>