Because it was introducing dependency between the browser and the core 
of class. This is like having a popUp menu
in the middle of some deep class functionality.
Now we can do:

	Browser fullOnClass: Point

If we would have a package mechanism by default ***in*** squeak. Then 
we could express that
browse is added on Class and on Object when the Browser package is 
loaded. And we could get a small Class/Object
when we do not have the Browser loaded. I think that at the nothing is 
wrong to have browse in Object or Behavior
except that this induces a completely different strategy to manage 
mess: this is related to the idea of having a build
process out of packages to create an image versus stripping it (with 
all the problems you get).

Stef


On 4 mars 04, at 18:06, Masashi Umezawa wrote:

> Hi,
>
> In Squeak 3.5,
>
>     1 class browse.
>
> will open a Browser on SmallInteger.
>
> But, from 3.6, it raises MessageNotUnderstood error, because
> Behavior>>browse has been removed.
>
> Are there reasonable reasons to remove this method?
> I think #browse is handy. Both VW and Dolphin will open a Browser
> in the example code. (even "1 browse" works).
>
> Cheers,
> ---
> [:masashi | ^umezawa]
>
>