BudVVeezer

9 ms·

31.
by BudVVeezer 11y ago
I think this is a good step in the right direction, but still falls short. For instance, it's heavily gender binary, and has odd cultural mismatches such as "man with turban" but no "woman with hijab." However, majo
32.
by BudVVeezer 11y ago
It's something we're discussing and exploring. The general thought is that Clang could do this for everything but sized deallocations (and it's unclear how much of an issue those would pose).
33.
At one fell swoop(phrases.org.uk)
14 points by BudVVeezer 11y ago|6 comments
34.
by BudVVeezer 11y ago
I apologize for being imprecise. We're aware it's more than just ADL or constexpr, but we had insufficient time to address it at this meeting. It's definitely on our radar, we flagged it as a high priority item.
35.
by BudVVeezer 11y ago
This topic was discussed in Lenexa at last week's C++ standards meeting, and the direction the core working group was thinking was that this should be ill-formed, but is currently under specified. I would not rely on this ADL constexpr
36.
Top 30 Targeted High Risk Vulnerabilities(us-cert.gov)
1 points by BudVVeezer 11y ago|0 comments
37.
by BudVVeezer 12y ago
One of the two values (a or b) gets evaluated twice. Eg) min(a++, b++); a or b would really be incremented twice.
38.
by BudVVeezer 12y ago
If you are investigating the CERT coding standards, I would recommend focusing on the rules more than the recommendations. The rules are normative and give excellent advice on how to write secure code. The recommendations are generally more
39.
by BudVVeezer 12y ago
It can, and it is. One of the outcomes of the CERT C secure coding standard was the publication of TS 17961, which is an ISO document on C analyzability, which also went hand in hand with the Annex L (normative) section of the C standard. B
40.
by BudVVeezer 12y ago
I just tried the following simple example: #include <string.h> struct S { int i; char c; int j; }; void f(void) { struct S s1 = { 0, 0, 0 }, s2 = { 0, 0, 0 }; memcpy(&s1, &s2, 9); } int mai
41.
by BudVVeezer 12y ago
It's shocking to see how often people write code like: memcpy(somePtr, &myStructObj, 12); So while that warning can certainly be useless information, it does definitely catch bugs. Unfortunately, the people who write code like the
42.
Control Flow Guard security feature(blogs.msdn.com)
2 points by BudVVeezer 12y ago|0 comments
43.
by BudVVeezer 12y ago
Try it with -stdlib=libc++, since that's what will control the behavior of std::string.
44.
The First Known Case of Virus-Attacks-Virus (2009)(discovermagazine.com)
2 points by BudVVeezer 12y ago|0 comments
45.
How to convert an old washing machine into a water powered generator(youtube.com)
1 points by BudVVeezer 12y ago|0 comments
46.
by BudVVeezer 12y ago
Except that it was a collaborative effort that involved far more than just Microsoft, such as CERT, and the WG14 committee as a whole...
47.
by BudVVeezer 12y ago
When I tried to change my password to a twenty character pass phrase, I wasn't allowed because it was "too weak". Adding a single digit made it "strong." I am not particularly comforted by this.
48.
Pyro Board: 2D Ruben's Tube(youtube.com)
4 points by BudVVeezer 12y ago|0 comments
49.
by BudVVeezer 13y ago
We tested most of the major ones at work on the faulty code, and only PC-Lint caught the issue.
50.
The Trouble with Mrs Hughes(bibliocurio.wordpress.com)
2 points by BudVVeezer 13y ago|0 comments
51.
by BudVVeezer 13y ago
Odd that there's no mention of Annex K support under the "Security/hardening comparison" heading. While it's optional to implement, it certainly applies.
52.
by BudVVeezer 13y ago
I'll ignore your ad hominem and simply point out that Tim (the person who commit the AArch64 backend from the post I linked) is an Apple employee...
53.
by BudVVeezer 13y ago
A quick search for ARMv8 and AArch64 in the LLVM commits list shows that a considerable amount of work has been happening on this front. In fact: http://lists.cs.uiuc.edu/pipermail/llvm-commits/Week-of-Mon-... I w
54.
by BudVVeezer 13y ago
I am entirely uncertain of why this was downmodded. The _s functions are part of the C standard (Annex K), and truly are better replacements for their counterparts. It's unfortunate that the glibc maintainers have shown so little inter
55.
by BudVVeezer 13y ago
sizeof(char) is implementation defined; see limits.h for more information on the probable size of char for your target. If the sizeof(char) is 1, the division will be optimized away, so there's no loss by keeping the code portable.
56.
by BudVVeezer 13y ago
Was anyone else a bit put-off that it was the patrol car that killed the cyclist, and not the person driving the patrol car (as it would have been reported had it not involved an officer)?
57.
by BudVVeezer 13y ago
Microsoft led the standardization process for the Annex K functions.
58.
by BudVVeezer 13y ago
Those aren't "Microsoft functions"; they're C's optional Annex K functions which Microsoft happens to mostly implement (though in true MS fashion, they did manage to get a few wrong before the standard was finalized
59.
Implementing a four-bit adder with C++ template metaprogramming(blog.aaronballman.com)
1 points by BudVVeezer 13y ago|0 comments
60.
by BudVVeezer 13y ago
Every TSA checkpoint I've ever been through has had an armed police officer there. So what's this "call for armed guards"?

More ›