Timeline for regex string extension
Current License: CC BY-SA 3.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Feb 22, 2017 at 7:59 | vote | accept | Matthias Burger | ||
| Feb 8, 2017 at 14:45 | answer | added | t3chb0t | timeline score: 1 | |
| Feb 8, 2017 at 14:39 | comment | added | Matthias Burger |
a lambda with so many parameters will be (IMO) pretty hard to read good point! Mh I think I will go with only 4 parameters. I don't think I will ever use more than 4 groups... otherwise I simply will use the Regex-class if I got more than 4 params
|
|
| Feb 8, 2017 at 14:35 | comment | added | Adriano Repetti |
Honestly I'd stop with 2 overloads (3 at maximum). At the calling point a lambda with so many parameters will be (IMO) pretty hard to read and a traditional approach preferable. Well, it's just my POV. Note that nothing stops you to have an extra Func<string[], string> overload (sacrifyng readability)
|
|
| Feb 8, 2017 at 14:22 | comment | added | Matthias Burger |
@AdrianoRepetti would be nice to have something like params for generics. would save me a lot of code...- so you wouldn't change anything and just go with e.g. 10 overloads?
|
|
| Feb 8, 2017 at 14:19 | comment | added | Adriano Repetti |
What's bad with those overloads? If you need an extra parameter you just add it to your lambda, no need to also change method name (PatternReplace1, PatternReplace2, etc? nooo)
|
|
| Feb 8, 2017 at 14:16 | history | asked | Matthias Burger | CC BY-SA 3.0 |