DCoder -: um, lets say variable q is stored in the memory at 0x012345, then a pointer to variable q will contain 0x012345
MadIvan : does that mean that if q changes, so will the pointer to it change?
DCoder -: it stores the q's location, not the value
Renegade: woah, so much talk at this time of the day?!
MadIvan : 6:31AM here :P
DCoder -: same here
MadIvan : so what the purpose of the pointer then?I mean, why not have a second variable?
Renegade: I just watched Femme Fatale
Renegade: and could predict all important plot points
Renegade: so, while it was entertaining, it was boring at the same time
Renegade: then again, it had Rebecca Romijn lesbian sex, so who am I to complain?
DCoder -: if you have a function that takes a big struct as a parameter, what is more compact, sending it 4 bytes (an address of struct) or the entire struct?
MadIvan : 4 bytes
MadIvan : ah, i kind of get it now :P
DCoder -: :)
DCoder -: also, when you send the entire struct as a param, a *copy* of the struct is made, thus the original copy does not get changed
DCoder -: kinda bad when you want your function to change something in it
Renegade: you know, when I tell you about Rebecca Romijn having lesbian sex, and you continue to talk about c++/asm memory pointers as if nothing happened, I'd take that as a sign for a serious sexual disorder