As purely a side note:
I stuffed a lot of date/time/datetime/timestamp code i use into wrappers in a central module of my framework. It's not the best for performance, but it helps during testing. It's quite astonishing for how much timestamp based crap you have to test in commercial 24/7 applications, including leap years, DST changes etc.
And plainly wrong system times, because some clueless admin didn't understand NTP and firewalled it. And just playing with the system time isn't enough, because the database server in production might have a different time than the application server. During dev, everything runs on a single laptop, so i need a single place where i can fudge the time functions in Perl, so i can test if i accidently mix local and remote timestamps...
In reply to Re^6: What's so wrong with this (dereferencing)code?
by cavac
in thread What's so wrong with this (dereferencing)code?
by Maelstrom
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |