Home/ Questions/Q 6383311
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-25T02:38:02+00:00

This is a question more about best practices/design patterns than regexps. In short I

  • 0

This is a question more about best practices/design patterns than regexps.

In short I have 3 values: from, to and the value I want to change. From has to match one of several patterns:

XX.X
>XX.X
>=XX.X
<XX.X
<=XX.X
XX.X-XX.X

Whereas To has to be a decimal number. Depending on what value is given in From I have to check whether a value I want to change satisfies the From condition. For example the user inputs “From: >100.00 To: 150.00” means that every value greater than 100.00 should be changed.

The regexp itself isn’t a problem. The thing is if I match the whole From against one regexp and it passes I still need to check which option was inputted – this will generate at least 5 IFs in my code and every time I want to add another option I will need to add another IF – not cool. Same thing if I were to create 5 Patterns.

Now I have a HashMap which holds a pattern as the key and a ValueMatcher as the value. When a user inputs a From value then I match it in a loop against every key in that map and if it matches then I use the corresponding ValueMatcher to actually check if the value that I want to change satisfies the “From” value.

This aproach on the other hand requires me to have a HashMap with all the possibilities, a ValueMatcher interface and 5 implementations each with only 1 short “matches” methode. I think it sure is better than the IFs, but still looks like an exaggerated solution.

Is there any other way to do it? Or is this how I actually should do it? I really regret that we can’t hold methods in a HashMap/pass them as arguments because then I’d only have 1 class with all the matching methodes and store them in a HashMap.

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    How about a chain of responsibility.

    Each ValueMatcher object exactly one From/To rule and a reference to the next ValueMatcher in the chain. Each ValueMatcher has a method which examines a candidate and either transaforms it or passes it on to the next in the chain.

    This way adding a new rule is a trivial extension and the controlling code just passes the candidate to the first member of the chain.

    • 0