standards

I have the following question: How are anonymous structures (or unions) properly initialized according to the current C1X draft ? Is this legal: struct foo { int a; struct { int i; int j; }; int b; }; struct foo f = { 1, 2, 3, 4 }; struct foo g = { 1, { 2 }, 3 }; In GCC, g.j == 0 and g.b == 3 , while in tcc g.j == 3 and g.b == 0 . The current draft says: "[...] unnamed members of objects of structure and union type do not participate in initialization. Unnamed members of structure objects have indeterminate value even after initialization.". Can this be really true? Isn't struct foo h = { 0 };

I am wondering whether the following floating point notation is a valid JSON notation: "result":{"base_fee":1e-005} or should the exponent notation be replaced with a decimal notation? It is valid according to the format available at json.org as numbers can optionally have a base 10 exponent denoted by an E, uppercase or lowercase, an optional plus or minus, and one or more digits. It's perfectly valid, according to RFC 4627 RFC 7159 *: The representation of numbers is similar to that used in most programming languages. A number contains an integer component that may be prefixed with an

Does the C++ standards committee provide (on the open standard site or elsewhere) any indicatation of the status of the papers under consideration and indexed on the open-standards site? I am referring to the individual "papers" indicating potential changes to the standard, with associated discussion, as per the example below; I am not referring to the (published or draft) standard as a whole . For instance, how can I determine whether N3922 has been accepted or rejected? Shafik Yaghmour For this particular case, we can guess this is an Evolution Working Group( EWG ) issue from the Background

Is there an ISO standard address format? I can't seem to find one, and I'd like to know for object- and database-design purposes. (One interesting document that shows a bunch of formats is this: http://www.bitboost.com/ref/international-address-formats.html , but it's insane!) Jonathan Leffler No; each country defines its own standard. There have been a number of questions about this in times past, including: Best practices for storing postal addresses in an RDBMS Is there a common street address database design for all addresses of the world The second of those itself has references to a

How to implement URL Routing in PHP. Vinko Vrsalovic If you use Apache you can do the URL routing via mod_rewrite. Small example: RewriteEngine On RewriteRule ^(dir1)/?(path2)? main.php?dir=$1&path=$2 That'll have any request like http://yoursite.com/dir1/path1 served by http://yoursite.com/main.php?dir=dir1&path=path2 More examples here . The other alternative have every request redirect to a single php file RewriteEngine On RewriteRule (.*) main.php?request=$1 and then to do it in code, where you can use a similar approach , by having a set of regular expressions that are matched by some

C standards talk about constraints , e. g. ISO/IEC 9899:201x defines the term constraint restriction, either syntactic or semantic, by which the exposition of language elements is to be interpreted and says in chapter Conformance If a ‘‘shall’’ or ‘‘shall not’’ requirement that appears outside of a constraint or runtime-constraint is violated, the behavior is undefined. In chapter Environment , Subsection Diagnostics it is said A conforming implementation shall produce at least one diagnostic message (identified in an implementation-defined manner) if a preprocessing translation unit or

Code I've got a function which I can write in one of the four possible ways: int do_or_die(int retval); int do_or_die(ssize_t retval); ssize_t do_or_die(int t retval); ssize_t do_or_die(ssize_t retval); And then it will be called with both of these ways for library functions: written = do_or_die(write(...)); // POSIX write returns ssize_t printed = do_or_die(printf(...)); // printf returns int Questions Which prototype should I use? What types should I give to written and printed ? I want to have the most robust and standard code, while still having just one do_or_die function. I am using C99

For types T for which std::is_floating_point<T>::value is true , does the C++ standard specify anything on the way that T should be implemented? For example, does T has even to follow a sign/mantissa/exponent representation? Or can it be completely arbitrary? From N3337: [basic.fundamental/8]: There are three floating point types: float, double, and long double. The type double provides at least as much precision as float, and the type long double provides at least as much precision as double. The set of values of the type float is a subset of the set of values of the type double; the set of