Rob Bank wrote:After having looked more closely at your suggestion Stephan; wow, that's really elegant and strong! In my current code I'm doing some other text modifications also (before what I'm trying to accomplish with my regex line discussed here), and can conclude that transferring that stuff to this Participant object would make things much more transparent and likely less buggy. Appreciate very much also the level of customization!! Wow.
Rob Bank wrote:Why the colon in %s:? This would imply lastName's are followed by a colon, no?
Row 5-6: in my head, the ending parentheses shouldn't be there. E.g. id is a variable, not a method, no?
nothing after it compiles
Rob Bank wrote:(nice to learn that try blocks take care of the closing by default!)
mPoint is short for matcherPoint. I see a lot of Pattern p = … and Matcher m = … so this seemed like a suitable naming - switching.
If I understand correctly, e.g. lines 25-33 should be put outside the if-bracket. I guess this is readability related / common praxis more than computationally significant?
But cities is neither really really cities - it can be a club or a city or whatever the results uploader decides to put there. I have seen up to three words used on occasion; however mostly it is null. Let’s call it a property of the participant that in theory can be anything between zero and n strings.
Course & letter[/i] is the official naming, where the letter stands for level of challenge in alphabetically ascending order. If you’re feeling invincible, run the toughest Course A.
... (i) not if there are more than two participants sharing a place and (ii) not if there is additionally, say, in course B, a shared place.
Rob Bank wrote:Yes, ONE thing / property. The choise of commas; can't recall any particular reason for it at start of project, other than that's the data separation formatting on file orders and generations at work and that it would be the best format considering a possible future database setup.
I’m basically reading the source code of a URL. As far as I understand from a googling, that is the HTML request body, no? Don’t have access to my code currently so can’t say how it’s done technically.
I’m curious as to why you prefer calculating place and difference instead of reading them. I guess I will find that out while looking closer at your code though.
Robert and Mick sharing place but having different point was an example of what I was trying to fix with my arrow anti-pattern loop.
At URL read and corresponding txt file write, .replaceAll(" +", ",") gives ...,New,York,...