On 18.06.2024 11:35, Rick McGuire wrote:
All of the trace entries that format a value into the message pass through
RexxActivation::traceTaggedValue(), which then calls RexxActivation::traceOutput(), where the
trace object is created. Just pass the name and value along to traceOutput() as arguments and set
them as properties in the TraceObject if they're non-null.
Thank you for this information! Will take a little while for me to turn to it (unfortunately, I have
a couple of urgent work related duties that I need to address in the next days, only thing possible
at the moment is to check and briefly communicate via e-mail).
---rony
On Tue, Jun 18, 2024 at 5:30 AM Rony G. Flatscher <rony.flatsc...@wu.ac.at>
wrote:
On 18.06.2024 02:09, Rick McGuire wrote:
> Dom's debugger has me thinking there should be some additional
information added to the trace
> object. One thing that would be quite useful for a debugger would be a
property that
provides the
> raw object that is included in the trace message.
Do you mean the receiver/target object in case of a traced message?
> Another thing that would be useful would be the name of the variable
being assigned or
referenced.
> This would make it easy, for example, to implement variable modification
breakpoints in the
debugger.
How would one go about implementing this efficiently (would not be able to
implement this by
myself,
hence the question)? If you could supply such an implementation or a sketch
thereof that would be
really very helpful!
---rony
_______________________________________________
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel
