tom@ghp.UUCP (Tom Huras) (10/15/88)
To all Smalltalk guruvah:
I'm just starting to play with Smalltalk (Apple's version 0.4) on a 1-meg
Mac SE. I was entering a new class method, complete with comments and
readable temporary variable names. When I accepted the method, the
comments vanished, and the variable names were re-named t1, t2,t3 and
so on.
Is there some flag or option switch I have to flip to prevent this?
The documentation I have doesn't seem to address this, and I'm not yet
comfortable enough to hack the system compiler classes to repair this.
All and any help appreciated...
--
"Wisdom is supreme; | Tom Huras, Gellman.Hayward & Partners Ltd.
therefore get wisdom. | 33 Yonge St., Toronto, Ontario, Canada, M5E 1G4
Though it costs all you have,| UUCP:{decvax|allegral|ihnp4|linus|utcsri}
get understanding." | !utzoo!mnetor!ghp!tom
Proverbs 4:7 | Disclaimer: These are only my opinions.mfox@hpbsla.HP.COM (Martin_Fox) (10/22/88)
Smalltalk has two options for handling requests for source code. It
can either 1) grab the source code off the disk and display it, or 2)
decompile the compiled version of the method and try to pass that off
as the source. Option 2 allows the system to save some space, as it
does not need to keep the source code around on the system. This also
means that comment disappear, and local variables must be renamed.
What you need to do is switch a global variable. Unfortunately I have
neither the documentation nor a SmallTalk system to play with :-( so
you are on your own. All global variables are contained in the dictionary
Smalltalk. Execute
Smalltalk inspect
to dig around in this dictionary. One of the variables should leap out
and yell "Set me! Set me!"
Caveats
I have only played with SmallTalk 80 on a Tek workstation.
It has been awhile.
I may not know what I am talking about.
Martin Fox
Planet Earth
Out here where the license plates all read
Famous Potatos.