At a cost of over a hundred lines of SHOUTY code (why does your code need to SHOUT?) compared to a handful of lines of code for 1nickt's alternative. In a production context 10 times the lines of code takes at least 10 times as long to write and 100 times as long to debug. It's also mutch more inclined to suffer NIH (Not Invented Here) syndrome which significantly increases maintenance effort. So lose, lose, lose really.
Optimising for fewest key strokes only makes sense transmitting to Pluto or beyond
| [reply] |
SankoR said it best: "you just enjoy letting people know you're a contrarian."
| [reply] |
So lose, lose, lose really.
Essentially. Portable, reliable and critically as far as any time based functions goes accurate code is infinitely preferable over a hodgepodge of unnecessarily hard to read ( $O, seriously? ) overly verbose spaghetti, which is neither portable nor reusable.
| [reply] |
| [reply] |