The "this" was the question — I have no doubts about bigup401 being an actual person because I have had the misfortune to work with outsource subcontractors who are like that guy. I once eventually gave up and rewrote an image-upload function that could not preserve aspect ratios for thumbnails. The rewrite collapsed half-a-dozen layers on the call stack to two, eliminating several wrapper functions that would accept thumbnail dimensions as arguments, ignore those arguments, and pass hard-coded values to the next function in the layer cake, which in turn ignores those values and passes different hard-coded values to the next function...
This questioner seems to chase fads, and I recently saw an article about item-scalping, so I suspect that he saw a similar article and decided to "get in the game" so to speak. It is one thing to be extremely thick, but bigup401 has combined being extremely thick with abusing the monastery as a free-as-in-beer code writing service and now seems to want code for less-than-honorable purposes. He is a blight upon our noble craft.
UPDATE: I had forgotten that each layer had different values, for that extra DailyWTF factor... — jcb
In reply to Re^3: continuously query
by jcb
in thread continuously query
by bigup401
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |