Altered method code displayed in browser after accept (3.4 #5170)

Doug Way dway at riskmetrics.com
Fri May 16 02:31:56 UTC 2003


Given that there is this more straightforward way to display in 
decompiled form, we should probably just get rid of the control magic 
key.  [FIX]es welcome.

- Doug Way


On Thursday, May 15, 2003, at 09:02 PM, Scott Wallace wrote:

> If you want to view a method in bytecode form or in decompiled form, a 
> better way, which doesn't rely on holding down a magic key, is to use 
> the "what to show" feature, which lets you view the code of any 
> browser or message-list in any of ten different forms.
>
> One if these ten is "source", which yields what you normally see -- 
> the actual source code.
>
> Another is "decompile."
>
> Another is "byteCodes."
>
> Then there are seven others to check out ;=)  Some of these are 
> extremely useful; others are suggestive of possible futures.
>
> You can choose which of the ten code-forms to use in a code tool in 
> three different ways:
>
> 1.  Use "what to show..." in the window menu.
>
> 2.  Use "what to show..." in the method-list menu.
>
> 3.  Click on the rightmost button in the button pane; this 
> square-cornered button reports on the current "what to show" setting, 
> and hence usually says "source".
>
> The "what to show" menu can be made permanent (i.e. "pinned,") which 
> is convenient if you want to explore what the different code-forms > are.
>
> Cheers,
>
>   -- Scott
>
> PS:  The "what to show" feature is available not only in every browser 
> and message-list, but also in the "Change-set browser" and the 
> "Message Names" tool.
>
>
> At 3:36 PM -0700 5/15/03, Nevin Pratt wrote:
>> Ned Konz wrote:
>>
>>>
>>> If you have the shift key down, you'll see a decompilation. But the 
>>> variable names should still be intact.
>>>
>>>
>>
>> I used to do this with VisualWorks (hold shift key down to see the 
>> bytecodes of the method).  In fact, once it was an *invaluable* trick 
>> in finding an obscure GemStone/VisualWorks/Envy interaction bug.  I 
>> didn't know the Squeak browsers would do that.
>>
>> Hmm, I just tried it with a System Browser (Squeak 3.4-5170, on 
>> RedHat 8.0).  Hold shift key down, click the method name in the top 
>> right pane while holding shift down.
>>
>> Doesn't work.  Doesn't seem to make any difference.
>>
>> So, how do you do that again?
>>
>> Nevin
>



More information about the Squeak-dev mailing list