|
Gesundheit!
If you have an important point to make, don't try to be subtle or clever. Use a pile driver. Hit the point once. Then come back and hit it again. Then hit it a third time - a tremendous whack.
--Winston Churchill
|
|
|
|
|
From android core
public List<ResolveInfo> queryBroadcastReceivers(Intent intent,
@ResolveInfoFlags int flags, @UserIdInt int userId) {
Log.w(TAG, "STAHP USING HIDDEN APIS KTHX");
return queryBroadcastReceiversAsUser(intent, flags, userId);
}
modified 20-Oct-19 21:02pm.
|
|
|
|
|
|
Dates.
A date is represented as either a floating point value or "datetime". So far so good.
I set the date to 0, and the resulting datetime representation was null. Hmmmm.
I set it to 1, and the datetime was 31 Dec 1899. Well, okay... I guess.
The real adventure starts when you try to find the absolute max datetime that can be represented. There is no documentation that I could find that says what this value is, and I think I know why.
That value is 313740917827896, or 31 Dec 4294967295.
If you add 1 to the numeric value, the represented datetime becomes 01 Jan 0000.
If you continue adding, you can go all the way to 313740918558381, which gives you a datetime of 31 Dec 1999.
If you add 1 to that value, it finally overflows into something that evidently cannot be interpreted as a date.
If you really want a laugh, I changed that absolute max value to a negative number, and I got a datetime of 4294967292 Jan 1900. Yes, that first number is the DAY. Curiously, it's almost the same value as the max possible year (before it wraps around).
I don't know whether to laugh or cry...
".45 ACP - because shooting twice is just silly" - JSOP, 2010
- You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
- When you pry the gun from my cold dead hands, be careful - the barrel will be very hot. - JSOP, 2013
modified 31-May-17 14:45pm.
|
|
|
|
|
January 1900 was clearly a very long month.
Where were you on 42884th Jan 1900?
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
AntiTwitter: @DalekDave is now a follower!
|
|
|
|
|
So I was texting this cute girl when she asked me "What's your perfect date?"
I said "dd-MM-yyyy, anything else is just confusing."
She never texted back
|
|
|
|
|
She probably was used to MM/dd/yyyy and didn't want to confuse you even more
--
"My software never has bugs. It just develops random features."
|
|
|
|
|
Seems like I've dodged a bullet then!
|
|
|
|
|
All of you are wrong, yyyy-mm-dd is objectively the best format.
|
|
|
|
|
No it's not, why start with a number that only changes once in a millenium?
The least you could do is stick that somewhere in the middle!
Start with the day, however, and you'll probably never have to read past the first two digits
|
|
|
|
|
I don't understand why you're so in love with numbers. Nothing beats localized text so better to use "dddd d MMMM yy". It's just so readable and drops the unnecessary century. We're all at the same millennia here, right?
|
|
|
|
|
Great idea, that is now the default format in all my applications
|
|
|
|
|
Sander Rossel wrote: No it's not, why start with a number that only changes once in a millenium?
Because its sortable as text. That's basically the whole point with making it THE standard. ISO 8601 - Wikipedia[^]
|
|
|
|
|
Real men sort on substrings!
And the really very manly men sort Wendelius' format
|
|
|
|
|
That format is the most sortable.
".45 ACP - because shooting twice is just silly" - JSOP, 2010
- You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
- When you pry the gun from my cold dead hands, be careful - the barrel will be very hot. - JSOP, 2013
|
|
|
|
|
It also conforms to ISO 8601.
|
|
|
|
|
"Can I compare thee to a summer's day?"
Because July the 17th was quite nice, and ... where are you going?
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
AntiTwitter: @DalekDave is now a follower!
|
|
|
|
|
Kill it! Kill it with fire!
What do you get when you cross a joke with a rhetorical question?
The metaphorical solid rear-end expulsions have impacted the metaphorical motorized bladed rotating air movement mechanism.
Do questions with multiple question marks annoy you???
|
|
|
|
|
I can understand exploring the min value boundaries but extending your research to those lengths is just cruel. I obviously dodged a bullet when I delegated that particular load if crap to another developer.
Never underestimate the power of human stupidity
RAH
|
|
|
|
|
|
I'm not sure how something in C# is applicable to the sh|t stain we all know as Qlikview.
".45 ACP - because shooting twice is just silly" - JSOP, 2010
- You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
- When you pry the gun from my cold dead hands, be careful - the barrel will be very hot. - JSOP, 2013
|
|
|
|
|
Just me assuming you were using it via an interface
|
|
|
|
|
Qlikview is a stand-alone app with no support for plug-ins, or even real coding talent, although it requires one to be able to figure out workarounds for their arbitrary restrictions, numerous limitations, and bugs that they prefer to call "nuances".
As a programmer, Qlikview's "programming" features are an affront to my developer sensibilities. If anyone on the planet was in danger of having physical harm inflicted on them from a carefully aimed shot, it's the sub-humans that invented Qlikview.
".45 ACP - because shooting twice is just silly" - JSOP, 2010
- You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
- When you pry the gun from my cold dead hands, be careful - the barrel will be very hot. - JSOP, 2013
modified 1-Jun-17 10:10am.
|
|
|
|
|
Thank you for making the mess I code in seem reasonable.
<cowardly lion="">"I do love my job, I do love my job. I do, I do, I do, I do I do love my job!"
|
|
|
|
|
Sounds like it's even worse than Crystal Reports then.
|
|
|
|