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 20740] - [PATCH - Updated] Map.debugPrint assume key is string.
Date Mon, 25 Aug 2003 18:35:12 GMT
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=20740>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=20740

[PATCH - Updated] Map.debugPrint assume key is string.

apacheBugzilla@AMammenT.cotse.net changed:

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



------- Additional Comments From apacheBugzilla@AMammenT.cotse.net  2003-08-25 18:35 -------
I disagree with two things in the changes made to my patch, though a bunch of 
the others are great!   I also have a question about one of your comments.... 

1) Some maps are allowed to have null keys.  Since the label field, during 
recursion, contains the key, the guard within verbosePrintInternal as 
currently stated will not print out any entry associated with a null key.  

2) I think that even when a nested map is present, the type of the map should 
be printed out in debug mode.  

3) You note that, in dealing with nested maps, it would make sense to have a 
stack.  I can see that - otherwise, there's the possibility of infinite 
recursion.  Is it acceptable to add an internal stack, and then add 
synchorization to the stack within utilities of this sort?

Mime
View raw message