search

jlabbe-processia / mxupdate

Automatically exported from code.google.com/p/mxupdate
1 stars 1 forks source link

Calculated Symbolic Names must avoid special characters #137

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago 
What steps will reproduce the problem?
1.define new attribute with braces ( and )
2.export the attribute

What is the expected output? What do you see instead?
The calculated symbolic name includes ( and ), which results to "problems" if 
an central update is run.

Original issue reported on code.google.com by tim.mox...@googlemail.com on 19 Aug 2010 at 1:40

GoogleCodeExporter commented 8 years ago 
The "problem" with the braces comes from TCL:

Error (XXXXXXXXXXXX): bad variable name XXXXXXXXXXX: upvar won't create a 
scalar variable that looks like an array element

The name of the symbolic name is evaluated (and TCL variable names with ( and ) 
are used as array elements).

Original comment by tim.mox...@googlemail.com on 19 Aug 2010 at 1:42

GoogleCodeExporter commented 8 years ago 
Also ~ should be avoid because ~ are used as separator from some MX 
functionality.

Original comment by tim.mox...@googlemail.com on 19 Aug 2010 at 1:42

GoogleCodeExporter commented 8 years ago 
Currently

[^%&()+-0123456789:=ABCDEFGHIJKLMNOPQRSTUVWXYZ^_abcdefghijklmnopqrstuvwxyz~]

is defined as allowed characters...

Original comment by tim.mox...@googlemail.com on 19 Aug 2010 at 1:43

GoogleCodeExporter commented 8 years ago

Original comment by t...@moxter.net on 18 Nov 2010 at 9:01

GoogleCodeExporter commented 8 years ago 
Currently it is now

[^%&+-0123456789:=ABCDEFGHIJKLMNOPQRSTUVWXYZ^_abcdefghijklmnopqrstuvwxyz]

Original comment by t...@moxter.net on 14 Sep 2011 at 10:45

GoogleCodeExporter commented 8 years ago 
solved with r827

Original comment by t...@moxter.net on 15 Sep 2011 at 8:02

GoogleCodeExporter commented 8 years ago

Original comment by tim.mox...@innobix.com on 7 Feb 2014 at 8:30