[squeak-dev] Syntactic sugar for Transcript show:
Christoph.Thiede at student.hpi.uni-potsdam.de
Mon Dec 6 20:50:25 UTC 2021
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. :-)
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.
Von: Squeak-dev <squeak-dev-bounces at lists.squeakfoundation.org> im Auftrag von mail at jaromir.net <mail at jaromir.net>
Gesendet: Montag, 6. Dezember 2021 21:25:40
An: squeak-dev at lists.squeakfoundation.org; das.linux at gmx.de
Betreff: Re: [squeak-dev] Syntactic sugar for Transcript show:
I can't believe I copied the wrong example - indeed I meant
Transcript showln: self
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 :)
Thanks for your time,
Sent from Squeak Inbox Talk
On 2021-12-06T21:19:51+01:00, das.linux at gmx.de wrote:
> Hi Jaromir
> > On 6. Dec 2021, at 20:16, mail at jaromir.net wrote:
> > Hi all,
> > I'd like to propose two little unary helper methods to facilitate printing to the Transcript window. It would allow
> > #(1 2 3) transcriptShowln
> > in addition to
> > Transcript cr; show: #(1 2 3)
> > 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.
> > Similar implementation is present in Cuis or Pharo and a simple "print" command is usual in most languages (except a few like Java).
> > 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.
> > Object>>transcriptShowln
> > Transcript cr; show: self
> > Object>>transcriptShow
> > Transcript show: self
> > If there are no objections I'll send a changeset to the Inbox.
> I think
> Transcript showln: anObject
> is sufficient.
> If not, you always have Object>>printOn:
> Best regards
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Squeak-dev