variable-declaration

I started working with go for a few weeks, and (once again) I stumbled across something that seems odd for me: // Not working a := 1 { a, b := 2, 3 } // Works a := 1 a, b := 2, 3 playground I want to assign two variables simultaneously. One is already declared, in a superior scope, the other one is not. It does not work: the compiler tries to redeclare the former variable. However, it works fine if this variable is declared in the same scope. Why is that ? What you're experiencing is commonly known as "variable shadowing" . When you use := with any variable in an inner scope, including in

Is there a way to declare a variable like this before actually initializing it? CGFloat components[8] = { 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.15 }; I'd like it declared something like this (except this doesn't work): CGFloat components[8]; components[8] = { 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.15 }; You cannot assign to arrays so basically you cannot do what you propose but in C99 you can do this: CGFloat *components; components = (CGFloat [8]) { 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.0, 0.15 }; the ( ){ } operator is called the compound literal operator. It is a C99 feature. Note that in this

Today I found one interesting thing. I didn't know that one can't declare a variable after a goto label. Compiling the following code #include <stdio.h> int main() { int x = 5; goto JUMP; printf("x is : %d\n",x); JUMP: int a = 0; <=== giving me all sorts of error.. printf("%d",a); } gives errors like temp.c: In function ‘main’: temp.c:7: error: expected expression before ‘int’ temp.c:8: error: ‘a’ undeclared (first use in this function) temp.c:8: error: (Each undeclared identifier is reported only once temp.c:8: error: for each function it appears in.) Now what is the logic behind that? I

Does C++11 allow declaring non-static data members as 'auto' if they are initialized in the declaration? For example: struct S { auto x = 5; // in place of 'int x = 5;', which is definitely allowed }; GCC 4.7 rejects the above code, while it accepts int x = 5; . Assuming this is not a compiler bug but rather the standard really doesn't allow it, why not? It would be just as useful as declaring local variables auto . The rule for prohibiting non-static members is in 7.1.6.4 clause 4: The auto type-specifier can also be used in declaring a variable in the condition of a selection statement (6.4)

I'm new to VBA and want to know if I can convert the following declaration and assignment into one line: Dim clientToTest As String clientToTest = clientsToTest(i) or Dim clientString As Variant clientString = Split(clientToTest) Alex K. There is no shorthand in VBA unfortunately, The closest you will get is a purely visual thing using the : continuation character if you want it on one line for readability; Dim clientToTest As String: clientToTest = clientsToTest(i) Dim clientString As Variant: clientString = Split(clientToTest) Hint (summary of other answers/comments): Works with objects too

If you look at the grammar for *declarator*s in §8/4 you'll notice that a noptr-declarator can be written as ( ptr-declarator ), that is, it can be written as ( declarator-id ), which validates declarations like the ones in the title. As matter of fact this code compiles without a problem: #include <iostream> struct A{ int i;}; int (x) = 100; A (a) = {2}; int main() { std::cout << x << '\n'; std::cout << a.i << '\n'; } But what is the purpose of allowing these parentheses when a pointer (to an array or to a function) is not involved in the declaration? The fact that this rule is applicable in