So what the programmer really needs is to be educated about TreeMap?
Suutar
@Suutar
Best posts made by Suutar
Latest posts made by Suutar
-
RE: Yes Virginia, even more WTFs are real
-
RE: Pre-WTF: Help (dear god, help!)
a) this doesn't do offsite
b) fred goes out of town for a week and nothing's backing up his designated folder because he's not logging in
c) joe gets hit by a bus... can anyone get onto his system to get the backed up data?
d) this doesn't do incremental
e) a user has to be able to read a folder to use "make available offline". Be careful who's backing up payroll data.
f) this is not a system that is going to satisfy client requests if they know what's actually going on
-
RE: Yet another password WTF
There's not 720 permutations, there's 90.
Start with L1L2U1U2N1N2, where we can distinguish between the two members of each class. Then there's indeed 720 permutations. But since the two members of each class are really interchangeable, there's actually 1/8 as many, or 90.
-
RE: Insult to injury...
@Random832 said:
@Suutar said:
@Aaron said:
@DaveK said:
This is so common it's about time it was fixed in the language by specifying that a re-thrown exception should accumulate stack trace instead of wiping it out and starting again. Surely it couldn't be that hard to do in a backward-compatible way?
It's a common error, sure, but how do you propose they "fix" it? How is the language supposed to tell the difference between [code]throw ex[/code] and [code]throw new ArgumentNullException("data")[/code]?
Perhaps it could note that the token "ex" is the same token that was declared as the incoming exception?
And if it's not, it should assign the incoming exception to the InnerException of the one being thrown.
Ah, but that would break backwards compatability, wouldn't it? -
RE: Insult to injury...
@Aaron said:
@DaveK said:
This is so common it's about time it was fixed in the language by specifying that a re-thrown exception should accumulate stack trace instead of wiping it out and starting again. Surely it couldn't be that hard to do in a backward-compatible way?
It's a common error, sure, but how do you propose they "fix" it? How is the language supposed to tell the difference between [code]throw ex[/code] and [code]throw new ArgumentNullException("data")[/code]?
Perhaps it could note that the token "ex" is the same token that was declared as the incoming exception?
-
RE: "Just Daisy Chain"
If you can afford 2U, http://www.tsipower.com/DC-to-AC-Inverter.htm may be useful. As for daisy chaining... the vendor should be consigned to maintaining a thinnet installation.
-
RE: Ridiculus patents.
The problem is that the patent examiner doesn't know state of the art in all fields, so to them this might well not be self-evident. Sad, isn't it?
-
RE: Subnetting WTF.
actually...
the netmask chosen is indeed stupid. Insane even. A shooting offense.
The host address, however, is correct (and correctly labelled).
Look at the last octets:
IP is 204 = 11001100
subnet is 184 = 10111000
network is (ip and subnet) = 10001000 = 136
host is (ip and not subnet) = 01000100 = 68