Hi Thanks for your interest. Unfortunately I do not know how to check that.
In any event, as you see from my earlier email, I have worked around the problem now, Regards R Sent from my iPad > On 28 Dec 2021, at 15:34, Steffen Märcker <merk...@web.de> wrote: > > Hi Robert, > > have you checked that you're seeing the code you've typed and not just > decompiled methods? > > Best, > Steffen > > > Robert Briggs via Pharo-users schrieb am Montag, 27. Dezember 2021 11:43 > (+01:00): > > Hi > > I define temporary variables in a method, e.g. |e r |, e.g. in a unit test, > but when I run the test Pharo automatically replaces these with | tmp1 tmp2 |. > A similar thing happens with method arguments. For example methodName: > aString at: anInteger will become methodName: arg1 at: arg2. > > This has happened through my entire model, not just as described above. What > is going on. Is it a bug, or is there a setting that needs to be changed? > > Many thanks for any feedback on this. > > Regards > Robert Briggs > > -- > Gesendet mit Vivaldi Mail. Laden Sie Vivaldi kostenlos von vivaldi.com > herunter.
