standards

In C++ it is impossible to implement certain C++ standard library type traits without compiler intrinsics, using the C++ language only. Traits deal directly with C++ types. According to §17.6.1.3.2 freestanding implementations of the C++ standard library must implement <type_traits> . Doesn't this effectively mean that the C++ standard requires non-standard language extensions/compiler intrinsics from all compilers which support want to support freestanding C++ standard library implementations? Why were such type traits allowed into the standard without support in the core language? There are

Let us suppose I would like to read/write a tar file header. Considering standard C (C89, C99, or C11), do char arrays have any special treatment in structs, regarding padding? Can the compiler add padding to such a struct: struct header { char name[100]; char mode[8]; char uid[8]; char gid[8]; char size[12]; char mtime[12]; char chksum[8]; char typeflag; char linkname[100]; char tail[255]; }; I've seen it used in code on the web as well. Just freading, fwriting this struct to the file in one chunk, assuming there will not be any padding. Of course also assuming CHAR_BITS == 8 . I'm thinking

I've got two C strings that I want to append and result should be assigned to an lhs variable. I saw a static initialization code like: char* out = "May God" "Bless You"; . The output was really "May GodBless You" on printing out. I understand this result can be output of some undefined behaviour. The code was actually in production and never gave wrong results. And it was not like we had such statements only at one place. It could be seen at multiple places of very much stable code and were used to form sql queries. Does C standard allow such concatenation? Yes, it is guaranteed. Extract from

I'm a little confused about the new RDAP protocol and whenever it makes sense to pursue it any further. It looks to me like everyone agreed on it to be the successor of whois, but their databases seem empty. On ubuntu I tried rdapper, nicinfo and even their RESTful API: http://rdap.org/domain/google.com (this results in a "File not Found", but is correct according to here ) Am I misunderstanding something? Is RDAP dead, did the service not start yet or am I doing something wrong? Nicinfo returns this: nicinfo -t domain google.com # NicInfo v.1.1.0-alpha # Query yielded no results. [ NOTICE ]

As recently as 2002 the IETF was recommending in RFC 3406 that we should use x- prefixes for URN namespaces we didn't want to register, e.g. urn:x-acme:foobar . Now that the IETF has deprecated the x- prefix in RFC 6648 , how are we supposed to construct URNs for namespaces we don't intend to register? As an aside, I note that RFC 6648 specifically mentions URNs: "In almost all application protocols that make use of protocol parameters (including ... URNs ...), the name space is not limited or constrained in any way, so there is no need to assign a block of names for private use or

I have a question with whether or not this is a standard for using IComparer in C#. Say I have a situation in which there are three Person objects: P1, P2, and P3. Say I call the Compare method passing in P1 and P2 and the result is 0. This essentially means the two people should be categorized as equal. Now say I call the Compare method passing in P2 and P3 and the result for that is 0 as well. Again, this means the two people are equal. Logically speaking, one can assume P1 and P3 are equal as well; however, the Compare method could be implemented however someone decides to implement it. So