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

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.

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 <merkste@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.

On Mon, Dec 27, 2021 at 2:44 AM Robert Briggs via Pharo-users < pharo-users@lists.pharo.org> wrote: > 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. > Hi Robert, this kind of thing typically happens when the method source is "unavailable". In many Smalltalk implementations, you have *.sources and *.changes files to go along with the image file. There may be a problem with these files in your installation. Missing, not readable, corrupted, ... who knows what. In my Windows environment, the Launcher has put my images in C:\Users\myuserid\Documents\Pharo\images\. For example, I have a Pharo 9.0 - 64bit (stable) directory there with a number of files, including my *.image, *. sources, and *.changes files for that "project". Curiously, the image and changes files have the same basename, which matches the directory. The sources file has a slightly different name. > > 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 >