specifications

I'm wondering if there is any build-in support for the HTML5 Notification feature in Gecko browsers so far? Maybe some hidden developer thingy ? I'm aware of WebKits window.webkitNotifications which works great, so, is there a Firefox implementation ? Update After searching and reading some W3C HTML5 specs, I'm maybe a little bit off here. I can't find any Notification feature anywhere there. Am I facing wrong facts here? Is that just a "very own webkit implementation"? To start with your second question: no, it's not a WebKit-specific feature. But although a site called ‘html5rocks’ contains

One of the items in the Joel Test is that a project/company should have a specification. I'm wondering what makes a spec good. Some companies will write volumes of useless specification that no one ever reads, others will not write anything down because "no one will read any of it anyway". So, what do you put into your spec? What is the good balance between the two extremes? Is there something particularly important that really, really (!) should always be recorded in a specification? The best spec is one that: Exists Describes WHAT, not HOW (no solutions) Can be interpreted in as few ways as

I bumped into a problem, i hope someone can help me out :) I got a TextBox, and i want to limit users, so that they can't write multiple \ one after another. I'm using it for folders. For instance: C\temp\test\ Now I want to prevent input like: C\temp\test\\\ I've tried searching around for this problem, but I couldn't find anything like this, so I hope it's possible :) I don't really have any code to show, but here's the code for my TextBox: private void textBox1_TextChanged(object sender, EventArgs e) { try { Regex regex = new Regex(@"[^C^D^A^E^H^S^T^]"); MatchCollection matches = regex

The C++ spec ( http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2011/n3242.pdf , section 7.5.4) states that A linkage-specification shall occur only in namespace scope What exactly does "namespace scope" mean? Does this mean that a linkage-specification, such as extern "C" can't be in global scope, only in a namespace? What exactly does "namespace scope" mean? It means, that extern "C" should be only in namespace-scope (not class-scope, block-scope etc.) Something, that is not in namespace, but is in global scope - is in global namespace scope. The potential scope denoted by an original

In ECMA-262, 3rd edition [PDF] , under section 7.6 ("Identifiers," page 26), we see the following note: The dollar sign is intended for use only in mechanically generated code. That seems reasonable. Many languages commonly used for generating or embedding JavaScript hold a special meaning for $ , and using it in JavaScript identifiers within those languages leads to unexpected behavior . The "mechanically generated clause" appeared in edition 2. In edition 1, it was not present. As of edition 5, it disappears again without explanation, and it remains absent from the working draft of the 6th

In the following statement the val f is defined as a lambda that references itself (it is recursive): val f: Int => Int = (a: Int) => if (a > 10) 3 else f(a + 1) + 1 // just some simple function I've tried it in the REPL, and it compiles and executes correctly. According to the specification, this seems like an instance of illegal forward referencing: In a statement sequence s[1]...s[n] making up a block, if a simple name in s[i] refers to an entity defined by s[j] where j >= i , then for all s[k] between and including s[i] and s[j] , s[k] cannot be a variable definition. If s[k] is a value