Re: passing array of floats (or vectors) into another function - data scope - hmmm. Very ugly...

From:

Victor Bazarov <v.bazarov@comcast.invalid>

Newsgroups:

comp.lang.c++

Date:

Thu, 20 Oct 2011 08:13:48 -0400

Message-ID:

<j7p39s$hhd$1@dont-email.me>

On 10/19/2011 6:16 PM, someone wrote:

On 10/19/2011 10:34 PM, Jorgen Grahn wrote:

On Wed, 2011-10-19, someone wrote:

On Oct 19, 4:08 pm, Jorgen Grahn<grahn+n...@snipabacken.se> wrote:

On Mon, 2011-10-17, Victor Bazarov wrote:

There is no alternative to using global vars in that case, at least
not AFAIK - is this right or not?

Perhaps I used the word "global" a bit sloppily; it could e.g. be
something like:

int * get_the_data()
{
static int foo;
return&foo;
}

but that doesn't really help much.

Because that is not thread-safe ? Not sure I understand why "global" was
used sloppily, neither not sure of the purpose of this get_the_data()
function. Isn't this get_the_data() function a global function, so
instead foo could just as well be a global variable - the result is the
same: Ugly?

Foo is static, so it exists until the program terminates... Static is
not thread-safe, right? I think I can see that this doesn't really help
much, I'm just only 95% sure of the explanation...

Well, at least it does give you the ability to track (by adding some
kind of logging code) when access to the data is made. Beyond that,
there is no difference, I believe.

V
--
I do not respond to top-posted replies, please don't ask