And yet Pingit is still in the app store. https://itunes.apple.com/gb/app/barclays-pingit/id496552142
916 karma · joined February 27, 2009
And yet Pingit is still in the app store. https://itunes.apple.com/gb/app/barclays-pingit/id496552142
http://msdn.microsoft.com/en-us/library/aa664765(v=vs.71).as...
char dst[5];
sprintf(dst, "%.*s", (int)sizeof(dst)-1, "Hello!");
Copies a null-terminated string to dst, truncating if necessary to avoid overflow.Just don't forget the "." or the "-1".
"It's OK, it doesn't need any code changes, just a modification to the configuration files, so the approval process does not apply."
That company's developers just need to learn the trick of making the configuration file format Turing-complete.
If you don't have time to write your own interpreter, XSLT is an easy one to sneak by PHBs.
I've seen one system where 70-80% of the functionality was implemented in XSLT for this reason. It meant changes could be delivered in 5 days instead of 35. Obviously good news for the customer. The PHBs were pleased that the bug count in the C++ core had dropped (it hadn't really, we just stopped using the buggy modules.) The integration testers were pleased that the end product worked. Basically everyone was happy except the C++ reviewers in QA.
That is a bad idea, even if you are 100% certain the result was correct.
But there is (now) a better SE site for this: http://cs.stackexchange.com/
There is also http://www.linkedin.com/groups?gid=65767
Yes. And it is documented as such. Any dependency on repeatable iteration order is a bug.
That does not really belong to OO. You would be unlikely to find an AbstractSingletonBeanFactoryStrategy in a Smalltalk project for example (even one under the control of a Purist.) You would find it in a JavaEE project, but even then it is not part the platform, it has more to do with convention that has built up around the platform (and the type of Purists it attracts.)
https://www.schneier.com/blog/archives/2013/02/tide_becomes_...
It's the languages with very distinctive features that can be guessed quickly (assuming you have seen them before) e.g. cobol, erlang & also joke languages like intercal, brainfuck, chef etc.
Poor example. In Java, number + string means "convert the number to a decimal string then concatenate", and it can be invoked unintentionally.
A near-collision attack on double SHA256 (if you treat it as a single hash not a pair of independent hashes) would also crash bitcoin, but would not necessarily be a threat to use of SHA256 for authentication purposes.
A bitcoin block solution just needs the hash to include enough leading zeros. Authentication (nearly always being automated) requires every bit to match - hitting 255 of 256 bits is no better than hitting 0 bits, as either way your message will be rejected.