Static initialization in C ++ mixed with Objective-C

I have an iPhone game, a port from C ++ on other platforms. Thus, the user interface is encoded in Obj-C, but the main logic of the program is in several C ++ files. Some of these C ++ files have many global variables with initializers at the top.

Surprise! Debugging assumes that initialization never occurred. As if the Obj-C link doesn't know to call the old C ++ initialization chain. Does anyone know why this is necessary? A way to manually force these initialization procedures?

Ken

+3
source share

Source: https://habr.com/ru/post/1775698/


All Articles