On 17 Jan 2015, at 04:31, stepharo steph...@free.fr wrote:
Marcus
would not it make sense to emit a bytecode marker (kind of no-op) so that the
tools can get more information
about the encoded computation and get some abtsraction?
Honestly: tools should work on the AST level.
Hi,
Now GTInspector can inspect objects that use custom Slot definitions.
https://pharo.fogbugz.com/f/cases/14741/GTInspector-add-simple-slot-support
https://pharo.fogbugz.com/f/cases/14741/GTInspector-add-simple-slot-support
create a class with he TestSlot (where the ivar lives in
Excellent!
Alexandre
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
On Jan 16, 2015, at 10:59 AM, Marcus Denker marcus.den...@inria.fr wrote:
Hi,
Now GTInspector can inspect objects that use
Hi Marcus,
So now ' self class allSlots ' should be used also in the debugger to get
the instance variables of an object?
Cheers,
Andrei
On Fri, Jan 16, 2015 at 2:59 PM, Marcus Denker marcus.den...@inria.fr
wrote:
Hi,
Now GTInspector can inspect objects that use custom Slot definitions.
I guess so.
Doru
On Fri, Jan 16, 2015 at 3:28 PM, Andrei Chis chisvasileand...@gmail.com
wrote:
Hi Marcus,
So now ' self class allSlots ' should be used also in the debugger to get
the instance variables of an object?
Cheers,
Andrei
On Fri, Jan 16, 2015 at 2:59 PM, Marcus Denker
On 16 Jan 2015, at 11:28, Andrei Chis chisvasileand...@gmail.com wrote:
Hi Marcus,
So now ' self class allSlots ' should be used also in the debugger to get the
instance variables of an object?
Yes, at least for now… I am not yet that happy with the naming… it is hard to
get
For me it's ok like it is now.
I updated the GTDebuggers to use slots.
For example you can use the bytecode one to see what actually gets executed
(and even step into the code of the slot).
[image: Inline image 1]
Now the other problem is that because reading a slot uses #send:read: the
On 16 January 2015 at 14:59, Marcus Denker marcus.den...@inria.fr wrote:
change “iv” to value (e.g. 5).
How do you do that?
When I try iv := 5 in the inspector, it looks like it's changing a
local variable instead of the slot (as if the bottom field of the
inspector was a workspace)
--
Damien
On 16 Jan 2015, at 12:12, Andrei Chis chisvasileand...@gmail.com wrote:
For me it's ok like it is now.
I updated the GTDebuggers to use slots.
For example you can use the bytecode one to see what actually gets executed
(and even step into the code of the slot).
Screen Shot
On 16 Jan 2015, at 12:20, Damien Pollet damien.pol...@gmail.com wrote:
On 16 January 2015 at 14:59, Marcus Denker marcus.den...@inria.fr wrote:
change “iv” to value (e.g. 5).
How do you do that?
double click on the value… (it is a secret feature for now ;-)
When I try iv := 5 in the
On 16 January 2015 at 16:22, Marcus Denker marcus.den...@inria.fr wrote:
How do you do that?
double click on the value… (it is a secret feature for now ;-)
hhhaaa :)
it worked via writing an accessor method too
--
Damien Pollet
type less, do more [ | ]
On Fri, Jan 16, 2015 at 4:22 PM, Marcus Denker marcus.den...@inria.fr
wrote:
On 16 Jan 2015, at 12:12, Andrei Chis chisvasileand...@gmail.com
wrote:
For me it's ok like it is now.
I updated the GTDebuggers to use slots.
For example you can use the bytecode one to see what actually
Hi andrei
once it will be fully working I think that we will need a way to
activate it or not.
Because for most people Slots will be transparent. But your work is
great for slot designers.
Keep pushing.
Stef
Le 16/1/15 16:12, Andrei Chis a écrit :
For me it's ok like it is now.
I updated
Marcus
would not it make sense to emit a bytecode marker (kind of no-op) so
that the tools can get more information
about the encoded computation and get some abtsraction?
Stef
Le 16/1/15 18:22, Andrei Chis a écrit :
On Fri, Jan 16, 2015 at 4:22 PM, Marcus Denker marcus.den...@inria.fr
14 matches
Mail list logo
