static variables in C++ -vs- Objective-C

Question

As far as I remember, the keyword static, for C++, inside a function call meant that the static variable was initialized the first time the declaration was encountered.

I have used the static keyword in an Objective-C member function and the static variable seems to be initialized immediately (with a non-compile-time constant subscriber). Note, that I am coding in a mixed file type .mm of Objective-C.

- (id) init
{
    [self initSubsciber];
    [self relayMessages];
}

- (void) initSubscriber
{
    subscriber= PTR;
}

- (void) relayMessages
{
    // Example 2-2 (mspoller.c), 0MQ book pg.43
    // Initialize poll set
    static zmq_pollitem_t items[] = {
        { subscriber, 0, ZMQ_POLLIN, 0 },
};

In the above example, since I am calling initSubscriber before relayMessages, I would expect the subscribermember variable pointer to be equal to PTR, not NULL, because the zmq_pollitem_t line hasn't been called. Yet, it is NULL.

Has the behavior of static changed in the various versions of C++? And, how is the behavior defined in Objective-C in comparison?

Answer 1

No, C didn't change. That what you expect is how C++ works.

C

en.cppreference.com/w/c/language/storage_duration

Storage duration

[...]

• automatic storage duration. [...]

• static storage duration. The storage duration is the entire execution of the program, and the value stored in the object is initialized only once, prior to main function. All objects declared static and all objects with either internal or external linkage that aren't declared _Thread_local (since C11) have this storage duration.

C++

en.cppreference.com/w/cpp/language/storage_duration

Static local variables

Variables declared at block scope with the specifier static have static storage duration but are initialized the first time control passes through their declaration (unless their initialization is zero- or constant-initialization, which can be performed before the block is first entered). On all further calls, the declaration is skipped.

Objective-C++ (.mm)

.mm is Objective-C++, so C++ should apply. But that said there is no official specification of language. So to be sure move in .cpp files and leave only some interfacing code in the .mm. For example it's not clear whether/how the thread-safe local static work (Is it possible to remove dispatch_once in Objective-C++?).

What is Objective C++?

Also, you might want to read Apple's (sadly deleted, but archived) documentation on Objective-C++.

-- doches

Clang has a common unified parser for all C language family[5][6] and it looks like the single features are activated depending on the file type/extension and language standard support[7].

objective-c++