Issue 1351: OCompletion doesn't guess instVar in debugger context

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|

Issue 1351: OCompletion doesn't guess instVar in debugger context

cedreek
When coding in the debugger, and accessing directly an instvar, writing 
code after the instvar raises  a Message not understood as the debugger map 
is nil.

http://code.google.com/p/pharo/issues/detail?id=1351

--
Cédrick

_______________________________________________
Pharo-project mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Reply | Threaded
Open this post in threaded view
|

Re: Issue 1351: OCompletion doesn't guess instVar in debugger context

Johan Brichau
The problem here is that the instvar #debuggerMap is only referenced  
from this method. It is not intialized nor used anywhere else in  
Debugger.

If you replace this with 'self selectedContext debuggerMap', it works.

I will submit the fix.

On 21 Oct 2009, at 12:03, Cédrick Béler wrote:

> When coding in the debugger, and accessing directly an instvar,  
> writing
> code after the instvar raises  a Message not understood as the  
> debugger map
> is nil.
>
> http://code.google.com/p/pharo/issues/detail?id=1351
>
> --
> Cédrick
> _______________________________________________
> Pharo-project mailing list
> [hidden email]
> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

----------------------------
Johan Brichau
[hidden email]





_______________________________________________
Pharo-project mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Reply | Threaded
Open this post in threaded view
|

Re: Issue 1351: OCompletion doesn't guess instVar in debugger context

cedreek
Cool   Thanks Johan

2009/10/21 Johan Brichau <[hidden email]>
The problem here is that the instvar #debuggerMap is only referenced
from this method. It is not intialized nor used anywhere else in
Debugger.

If you replace this with 'self selectedContext debuggerMap', it works.

I will submit the fix.

On 21 Oct 2009, at 12:03, Cédrick Béler wrote:

> When coding in the debugger, and accessing directly an instvar,
> writing
> code after the instvar raises  a Message not understood as the
> debugger map
> is nil.
>
> http://code.google.com/p/pharo/issues/detail?id=1351
>
> --
> Cédrick
> _______________________________________________
> Pharo-project mailing list
> [hidden email]
> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

----------------------------
Johan Brichau
[hidden email]





_______________________________________________
Pharo-project mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project



--
Cédrick

_______________________________________________
Pharo-project mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project