>It's not standards-compliant
Why? It's just a VLA.
2,647 karma · joined March 24, 2012
>It's not standards-compliant
Why? It's just a VLA.
https://www.thurrott.com/windows/windows-10/4257/guys-seriou...
Not really. Windows 10 apparently allows universal Windows apps to call VirtualAlloc() and VirtualProtect().
http://blogs.msdn.com/b/chuckw/archive/2012/09/17/dual-use-c...
Are you sure? AFAIK you have to use C++/CLI which isn't C++ and the official examples are either C# or VB.NET: https://code.msdn.microsoft.com/site/search?f[0].Type=Topic&...
This article is also on GH (including some changes): https://github.com/Keith-S-Thompson/the-flat-trantor-society...
Well, he doesn't have to wait anymore:
https://trac.macports.org/wiki/FAQ#defaultprefix
>Why is /opt/local the default install location for MacPorts?
>additional floating-point characteristic macros (<float.h>)
VS2015 RC.
>querying and specifying alignment of objects (<stdalign.h>, <stdlib.h>)
Missing but the functionality is available as extensions.
>Unicode characters and strings (<uchar.h>) (originally specified in ISO/IEC TR 19769:2004)
VS2015 RC.
>type-generic expressions
Missing. (Use C++ instead. trollface.dds)
>static assertions
Missing but (incorrectly) static_assert can be used instead of _Static_assert.
>anonymous structures and unions
Partially or maybe even completely. I would have to check but for trivial usage I'd consider it to be complete.
>no-return functions
Missing but __declspec(noreturn) can be used instead.
>support for opening files for exclusive access
Missing but _fsopen() / _wfsopen() and _SH_DENYRW can be used instead.
>removed the gets function (<stdio.h>)
VS2015 RC.
>added the aligned_alloc, at_quick_exit, and quick_exit functions (<stdlib.h>)
Partially as aligned_alloc() is missing.
memset(&serv_addr, '0', sizeof(serv_addr));
That doesn't seem to be correct. The digit character 0 is not the same as the null character ('\0'). Just write 0 or use `struct sockaddr_in serv_addr = { 0 };`.>A review of libsqlite source code will demonstrate that it is written
>using many old practices of coping with "older systems". Many of the
>same techniques that caused unneccessary risk in OpenSSL.
From http://www.open-std.org/jtc1/sc22/wg14/www/C99RationaleV5.10..., PDF page 163:
>The Committee decided that gets was useful and convenient in those special circumstances when the programmer does have adequate control over the input, and as longstanding existing practice, it needed a standard specification.
But that doesn't matter that much since it was originally posted on 4chan and not DA.
The original can be found on the linked site, but it's also on DA: http://whynne.deviantart.com/art/Comic-Trolls-98357844
From the description:
>It's trollface, not coolface, but call it what you like.
That was just a codename. Vista and XP (and ME?) are actual examples.
>But this technique works only so long as the containing function (hack, in this example) does not exit.
Thompson went a step further by inventing the ++ and -- operators, which increment or decrement; their prefix or postfix position determines whether the alteration occurs before or after noting the value of the operand. They were not in the earliest versions of B, but appeared along the way. People often guess that they were created to use the auto-increment and auto-decrement address modes provided by the DEC PDP-11 on which C and Unix first became popular. This is historically impossible, since there was no PDP-11 when B was developed. The PDP-7, however, did have a few `auto-increment' memory cells, with the property that an indirect memory reference through them incremented the cell. This feature probably suggested such operators to Thompson; the generalization to make them both prefix and postfix was his own. Indeed, the auto-increment cells were not used directly in implementation of the operators, and a stronger motivation for the innovation was probably his observation that the translation of ++x was smaller than that of x=x+1.