Hi Stef,

...

The instance variable types are only detected in the Debugger, as a context is provided. In the case of Browser, Workspace etc. only "type suggesting" names do the job. But for instance variables this is not something people use.

strange because each time you send a message to an instance variable you would like to have a smart completion too.

Your right of course. What I was trying to say, is that people do not choose the name of instance variables to be "type suggesting".

For local variables I guess that a good heuristics to find the class is to look for what is in front of a new method :). Are you doing that?

Yes, If the type can't be found out I try two things. Examples: 1) a variable named "rectange" is made uppercase to "Rectangle" 2) or the first uppercase letter is searched. So aRectangle, asRectangle, myRectangle and so on would result in "Rectangle" again.

For Debugger and Workspace the type guessing is more accurate, as the context or the bound variables can be accessed.

on cincom store you have a package called roel typer ro something like that. All the code is available (ie one class and its tests :))

Ok, I'll have a look at it, thanks for the tip.

Ruben

On Monday, November 29, 2004, at 08:35AM, stéphane ducasse ducasse@iam.unibe.ch wrote:

hi ruben

I hope that we will have soon the simple typer of roel so we could get already some nice type information for instance variables.

...

Stef, Thanks for your feedback.

The instance variable types are only detected in the Debugger, as a context is provided. In the case of Browser, Workspace etc. only "type suggesting" names do the job. But for instance variables this is not something people use.

strange because each time you send a message to an instance variable you would like to have a smart completion too. For local variables I guess that a good heuristics to find the class is to look for what is in front of a new method :). Are you doing that?

...

I planed to add the guessing of instance variables types for the next version in the following way: Analyze the initialize method with the RBParser. You see a solution in analyzing the bytecode, is this what is working in Dolphin Completion?

I do not know. roel coded what he did in SOUL (kind of prolog) and hard-coded it in VisualWorks and his demoe last week was nice so I want to have that in squeak.

...

If you pass some pointers, I would very happy to try it out and eventually integrate it in eCompletion.

on cincom store you have a package called roel typer ro something like that. All the code is available (ie one class and its tests :))

...

Ruben

On Sun, 28 Nov 2004 22:19:28 +0100, you wrote:

...

this sounds quite cool Now I would like to know how do you sort the symbols. (I know that romain completion package is smarter that the default alt-q since he is paying attention to instance variables and also methods defined in the class (if I'm not wrong).

Now roel showed use a simple bytecode analyser that guess quite well the type of instance variables and this is on my to do list to port it to Squeak. )

So can you tell us more.

Stef

On 28 nov. 04, at 21:32, Ruben Bakker wrote:

...

The package is available on the SqueakMap with the name eCompletion. More information can be found on this page: http://homepage.mac.com/monique_bakker/squeak/eCompletion.html.

Have fun... Ruben