On 2011-10-21 19:39, Peter Stuge wrote:
Not so easy. I disagree with reverting the patch without having a
clear plan for the real fix.
Not easy because it is not neccessarily possible to implement the
same functionality in any other way.
The proper solution requries Jim expertise which I have none, or
possibly Tcl expertise which I have very very little. If pressed for
a solution, I would look into a workaround for the double evaluation,
such as a way to escape any \ in $filename.
But I disagree with reverting the commit. Fix the problem instead.
What?
So you don't know how to fix that, I don't know how to fix that, but we
cannot revert a one-line change that introduced A BUG just because it
(supposedly - I did not check) adds some functionality that was not
actually discussed in detail EVER?
Why can't we revert a change, fixing a bug and wait for a real
jimtcl-expert (Steve) to discuss other alternatives while in the
meantime OpenOCD would work as expected for Windows users?
"The problem" is that Windows paths now cannot be used normally and
OpenOCD cannot be used as before. Global variables thing which this
patch (supposedly) improves is just an improvement, because you could
use globals before anyway, just had to add "global NAME" before.
Please revert to fix a real problem (removing backslashes from Windows
paths). We can deal with improvement while at the same time OpenOCD
works as it should.
4\/3!!
_______________________________________________
Openocd-development mailing list
Openocd-development@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/openocd-development
