The future of Debug.monitor and Debug.trace

View: New views
1 Messages — Rating Filter:   Alert me  

Parent Message unknown The future of Debug.monitor and Debug.trace

by P T Withington-2 :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

I just added the following comment to http://jira.openlaszlo.org/jira/browse/LPP-7313 
:

> In particular, swf9 does not support 'watch'ing Object properties  
> (to allow it generally at runtime would impact performance  
> severely); so we can't provide it in the debugger dynamically. We  
> _could_ do something at compile time, e.g., we could add a property  
> to <attribute>, say monitor="true", that would let you recompile  
> your program and get the same effect as the current debugger call.  
> (Similarly, we could add a property to <method>, say trace="true",  
> that would trace calls to the method the way the current Debug.trace  
> call does.)

It is very likely, going forward to other runtimes, that they will  
also not support monitoring or tracing at runtime, so I am wondering  
how much people use these Debug features (or if they even knew about  
them)?

If you do use Debug.monitor and Debug.trace, would it be sufficient to  
replace them, as I outline, so they could at least be enabled/disabled  
by recompiling?

LightInTheBox - Buy quality products at wholesale price!