[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Subject: Fragment parsing
Lofton et al, according to the latest changes a lot more characters may show up in IDs or names. Especially the name attribute is not restricted with regard to usage of the space character. Consider the following fragments: #name(myName,view_context) #name(myName ,view_context) #name( myName ,view_context) #name( myName,view_context) These are four variations of a name with and without spaces as the first and/or last character. Right now, these are four DIFFERENT names, i.e. the names are in quotes: "myName" "myName " space at end is part of name " myName " spaces at start and at end are part of name " myName" space at start is part of name Is this the desired behavior for everybody, or should there be a rule that disallows leading and/or trailing spaces? BTW, this problem does not exist with IDs because the space is prohibited there. Dieter
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Powered by eList eXpress LLC