Hi all,
I have extended JimTCL to add the standard TCL "Trace" command, which allows
reading/writing target hardware registers simply via reading/setting TCL
variables. (see https://github.com/evanhunter/jimtcl )
This however creates a problem because OpenOCD currently has a proc named
"Trace" which performs a different function and which shadows the function in
JimTCL.
I'd like to suggest that the OpenOCD "Trace" function be renamed. (And any
other names which shadow standard TCL procs)
Regards,
Evan Hunter
------------------------------------------------------------------------------
Don't let slow site performance ruin your business. Deploy New Relic APM
Deploy New Relic app performance management and know exactly
what is happening inside your Ruby, Python, PHP, Java, and .NET app
Try New Relic at no cost today and get our sweet Data Nerd shirt too!
http://p.sf.net/sfu/newrelic-dev2dev
_______________________________________________
OpenOCD-devel mailing list
OpenOCD-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/openocd-devel
