variable-assignment

I tend to use the words define, declare and assign interchangeably but this seems to cause offense to some people. Is this justified? Should I only use the word declare for the first time I assign to a variable? Or is there more to it than that? Define and declare are similar but assign is very different. Here I am declaring (or defining) a variable: int x; Here I am assigning a value to that variable: x = 0; Here I am doing both in one statement: int x = 0; Note Not all languages support declaration and assignment in one statement: T-SQL declare x int; set x = 0; Some languages require that

Is it possible to declare multiple variables at once using Golang? For example in Python you can type this: a = b = c = 80 and all values will be 80. Yes, you can: var a, b, c string a = "foo" fmt.Println(a) You can do something sort of similar for inline assignment, but not quite as convenient: a, b, c := 80, 80, 80 VonC In terms of language specification, this is because the variables are defined with: VarDecl = "var" ( VarSpec | "(" { VarSpec ";" } ")" ) . VarSpec = IdentifierList ( Type [ "=" ExpressionList ] | "=" ExpressionList ) . (From " Variable declaration ") A list of identifiers

I've asked a similar question on structs here but I'm trying to figure out how C handles things like assigning variables and why it isn't allowed to assign them to eachother if they are functionally the same. Lets say I have two arrays: int x[10]; int y[10]; Why won't x = y compile? If they are both the same "signature" like that, then shouldn't you be able to assign them back and forth? Can I declare these in a way that would allow me to do that in C? It makes sense to me that you would be able to, but maybe there is a way that this can be done? Typedefs for structs seemed to be the solution,

Under what circumstances should I expect memcpys to outperform assignments on modern INTEL/AMD hardware? I am using GCC 4.2.x on a 32 bit Intel platform (but am interested in 64 bit as well). You should never expect them outperform assignments. The reason is, the compiler will use memcpy anyway when it thinks it would be faster (if you use optimize flags). If not and if the structure is reasonable small that it fits into registers, direct register manipulation could be used which wouldn't require any memory access at all. GCC has special block-move patterns internally that figure out when to

Am not new to JS or its syntax, but sometimes, the semantics of the language has me stumped at times. At work today, a colleague mentioned this: var a = b = []; is not the same as var a = [], b = []; or var a = []; var b = []; since the first version actually assigns the reference to an empty array to a and b. I couldn't quite accept this as true, but I'm not sure. What do you all think? Yes, they're not the same. var a = b = [] is equivalent to var a; b = []; a = b; Not only do both a and b get assigned the same value (a reference to the same empty array), b is not declared at all. In strict