New answers tagged

2

Probably because that's how regular expression flags are handled in most text editors and other programming languages. A lot of things about regular expressions make more sense when you're using them in a text editor such as vim, where almost all actions are keyboard-driven. For example, in vim if I type :s/foo/bar/g and press enter, all instances of foo ...


0

Nulls are problematic because they must be explicitly checked for, yet the compiler is unable to warn you that you forgot to check for them. Only time-consuming static analysis can tell you that. Fortunately, there are several good alternatives. Take the variable out of scope. Way too often, null is used as a place holder when a programmer declares a ...


0

I try to explain my experience with Java and the JNI. With Java you have a great language to create fast well and cross platform working applications. It's quite easy to understand and it works fine. But you know, if we're trying to use something like Audio IO , than Java fails. For this case we're using the JNI to implement IO over C++. For such things in ...


1

You have to have some code that follows the grammar. Perhaps as a simple case, this can be a simple set of recursive routines, one for each term in the grammar. You have to have a notion of the intermediate state of the parse, such as <term>: this can be part of the recursive state of the routines as they are executing. The parser goes a long for a ...



Top 50 recent answers are included