Difference between revisions of "Talk:Minigun/Incorrect maximum DPS/reply (6)"
Theaetetus (talk | contribs) m |
Theaetetus (talk | contribs) m |
||
Line 1: | Line 1: | ||
AFAIK, #switch can only check if a test value is ''equal'' to several case values -- it cannot make value comparisons, such as greater than or less than, which only #expr can. So if every #switch is going to have a #expr child, you might just as well just have an #if tree with nested #expr functions to save a chunk of CPU from following every false path. | AFAIK, #switch can only check if a test value is ''equal'' to several case values -- it cannot make value comparisons, such as greater than or less than, which only #expr can. So if every #switch is going to have a #expr child, you might just as well just have an #if tree with nested #expr functions to save a chunk of CPU from following every false path. | ||
− | I'm not familiar with #max or other extended parserFunctions, so I can't comment on feasibility there. To be quite honest, I'm not sure I'm even interested enough to develop the logic tree to do what the user is asking for if it was enabled and capable. Burnout is setting in rather hard from many users (OP not included) screaming, "the wiki sucks! nobody updates it" on IRC and Reddit while I dump 20+ hrs/wk into it, struggling to get it up to speed but always seemingly too many steps behind the devs. | + | I'm not familiar with #max or other extended parserFunctions, so I can't comment on feasibility there. To be quite honest, I'm not sure I'm even interested enough to develop the logic tree to do what the user is asking for if it was enabled and capable. Burnout is setting in rather hard from many users (OP not included) screaming, "the wiki sucks! nobody updates it" on IRC and Reddit while I dump 20+ hrs/wk into it, struggling to get it up to speed but always seemingly too many steps behind the devs. Edit: It's especially disheartening when you look at [[Special:RecentChanges]] and notice the lack of edits on the very same day people complain. |
Latest revision as of 09:04, 8 August 2016
AFAIK, #switch can only check if a test value is equal to several case values -- it cannot make value comparisons, such as greater than or less than, which only #expr can. So if every #switch is going to have a #expr child, you might just as well just have an #if tree with nested #expr functions to save a chunk of CPU from following every false path.
I'm not familiar with #max or other extended parserFunctions, so I can't comment on feasibility there. To be quite honest, I'm not sure I'm even interested enough to develop the logic tree to do what the user is asking for if it was enabled and capable. Burnout is setting in rather hard from many users (OP not included) screaming, "the wiki sucks! nobody updates it" on IRC and Reddit while I dump 20+ hrs/wk into it, struggling to get it up to speed but always seemingly too many steps behind the devs. Edit: It's especially disheartening when you look at Special:RecentChanges and notice the lack of edits on the very same day people complain.