Thread: where are static values stored?

Originally Posted by citizen

I don't want to claim that the compiler wouldn't optimize my snippet in the crude manner that you implied; however my snippet is not "in question." I was demonstrating my answer: That statics are stored in the same place as globals with access restrictions. My snippet was more of a test to see if you could globally poke at the value of something static. Had you not been able to, the assertion should have failed, (like it would for a pointer to a local automatic variable).

What you later stated is a possibility, but static variables cannot be destroyed at any point in run time (as dynamic ones can). As I stated, statics could be copied around from the function stack like you said. But the lifetime of the static variable is well defined, unlike a dynamic one: as long as from the point of initialization to the termination of your program. There's no need to explicitly manage static memory, and although implementors may opt to do that behind the scenes, I don't think that is the case for many. Personally, I wouldn't do it that way.

OP: c will live just as I described but it may point to other places in memory that make c invalid.

Well my point is basically that the question is a false one, he is not declaring a static
variable in this case, merely informing the compiler that the function returns an integer.

It's a fairly academic question to me anyway, my use of passing variable back and forth
between functions is somewhat 'limited' shall we say.

And in answer to the OP question, when function is called a second time it merely
retrives the return value of the stack as it did in the first call.

I mean how could you access this static variable any way?

Code:

int somevariable;

somevariable=do_something;

That is, I am fairly sure going to return an error similar to:-
"Oi!! you cannot do that, incompatible types, somevariable is an integer and do_something is a pointer to a function.

You *might* get away with:-

Code:

int somevariable;

somevariable=(int)do_something;

But I can't see it being of any use.

Originally Posted by vart

This is not a way to call a function in C. If you do not know this bit of info about C - why you still trying to answer any question here?

You just confusing people with such a crap.

I never implied it was a way to call a function hence the rest of your post is based up on
you initial false assumption and thus the 'crap' would appear to be a product of your own
mind.

Originally Posted by esbo

Well my point is basically that the question is a false one, he is not declaring a static
variable in this case, merely informing the compiler that the function returns an integer.

Originally Posted by esbo

I never implied it was a way to call a function hence the rest of your post is based up on
you initial false assumption and thus the 'crap' would appear to be a product of your own
mind.

If we ask you another time, will we get another answer?

Originally Posted by tabstop

If we ask you another time, will we get another answer?

Well you will get a reply, whether you get and answer depends to a large extent upon
whether your 'question' is comprehensible which unfortunately it is not on this occasion.
( obviously I mean comprehensibe to someone other than yourself).