tag:blogger.com,1999:blog-1973750947775262558.post7306570893026257027..comments2009-10-29T09:02:43.304-04:00bill sheltonhttp://www.blogger.com/profile/06624894387927690246noreply@blogger.comBlogger7125tag:blogger.com,1999:blog-1973750947775262558.post-45135390731225975722009-10-29T09:02:43.304-04:002009-10-29T09:02:43.304-04:00Just found this iterator solution via google. Perfect for a problem I&#39;m working on.<br /><br />I know it&#39;s only sample code, but perhaps worth a mention that ReFindVisitor.getFound() returns an empty array when nothing matches, rather than an empty struct. Easy to fix in a couple of lines (I&#39;ve got code if you want me to email).dr-nickhttp://www.blogger.com/profile/03132523772338483975noreply@blogger.comtag:blogger.com,1999:blog-1973750947775262558.post-89382286603279445562009-07-11T06:59:04.982-04:002009-07-11T06:59:04.982-04:00marc, great stuff and right on time! i was just looking into a way to recurse over the mxunit debug array to dump it to plain text. you took care of that and then some ... awesome!billyhttp://www.blogger.com/profile/06624894387927690246noreply@blogger.comtag:blogger.com,1999:blog-1973750947775262558.post-90030015780287885082009-07-10T22:32:40.077-04:002009-07-10T22:32:40.077-04:00HotJohn Allenhttp://www.blogger.com/profile/02063438353379239362noreply@blogger.comtag:blogger.com,1999:blog-1973750947775262558.post-46696319891666023362009-07-10T09:57:13.257-04:002009-07-10T09:57:13.257-04:00My thinking on this was very much influenced by the closure based each loops in ruby/groovy, which is why I was using a function in my approach. This definitely has limitations though, and I think your approach of using a an object as the visitor gives a lot more flexibility. Very nice!nmischehttp://www.blogger.com/profile/01625595898033904009noreply@blogger.comtag:blogger.com,1999:blog-1973750947775262558.post-2608396247915664482009-07-10T08:26:37.592-04:002009-07-10T08:26:37.592-04:00Most agreed. As you say, how many lines of code are we writing out there that essentially does the same exact thing! Seeing the pattern is what helps us cut down on redundancy.Ben Nadelhttp://www.blogger.com/profile/14054723593701580342noreply@blogger.comtag:blogger.com,1999:blog-1973750947775262558.post-53141096161440686092009-07-10T08:17:05.528-04:002009-07-10T08:17:05.528-04:00Ben, it&#39;s extremely similar to your custom tag solution. the only real differences are that it&#39;s component-based and that it recurses. But conceptually, they&#39;re quite similar.<br /><br />What I&#39;m trying to get better at when approaching a given problem is trying to see the solution in two ways: solving the specific problem, but also getting at the pattern of the problem, to see if I can solve that problem in such a way that I set myself up for an easier time of solving other problems in the future.Marc Esherhttp://www.blogger.com/profile/05942611191966201181noreply@blogger.comtag:blogger.com,1999:blog-1973750947775262558.post-41290140804247754432009-07-10T08:08:26.683-04:002009-07-10T08:08:26.683-04:00Looks cool. I like the stressing of thinking generically. Excellent point.Ben Nadelhttp://www.blogger.com/profile/14054723593701580342noreply@blogger.com