commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 31194] - [validator] Investigate removing <arg position=""> attribute
Date Fri, 12 Nov 2004 18:21:31 GMT
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=31194>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=31194

[validator] Investigate removing <arg position=""> attribute

dgraham@apache.org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|RESOLVED                    |REOPENED
         Resolution|FIXED                       |



------- Additional Comments From dgraham@apache.org  2004-11-12 18:21 -------
I could have used more than one day to comment on the patch :-).  I don't think
it accomplishes what we want.  It seems like the positions of default args
(those without a name) are kept separate from the positions of args with names.
 Since a message can use both named args and default args don't we need to keep
the positions in sync?  Also I think the positions should be grouped by the
arg's name.  As it is, it looks like each arg gets the next position regardless
of whether it's for a different message than the preceeding arg.

The goal is to get rid of the position attribute on the arg element.  If that's
not possible then the goal should be to limit how often the user must specify a
position.

---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org


Mime
View raw message