Hello, Maxim Rogozhin, you wrote: > Here is how time that such static storage to me was to be specified. I.e. it is the same dynamic storage? Give from the beginning. When process to it well certain amount of addresses of operative storage, cells of storage with an index I in a range [an is launched, b] to which he can address. Values an and b depend on digit capacity and OS. At process start there is an initialization in which course various things, including selection of storage for a stack (from address process above are fulfilled). Further somewhere it is necessary to allocate the objects which size is known before start. And this all global and static objects. Them is unnecessary to create and track lifetime is all solves for the developer the compiler. Here from the above described address space the area where all these objects are added is selected. Further there was a classification question (in other words how to refer to this area in the documentation). It called "static storage". Even in the course of performance of the program to the programmer the unknown at the moment of compilation an amount of any objects can be demanded. Well that is, their amount can dynamic change. Under these objects the programmer himself selects storage from address above. And itself releases - the compiler to it in it not the assistant. Further there was a classification question (in other words how to refer to this area in the documentation). It called "dynamic storage". As a rule with static they are nearby. For example, we admit at us address space [0, 100]. That static storage is can be [10, 20], and dynamic - [25, 90]. Therefore the answer to a question above "static is a same dynamic storage?" Depends on the point of view. From the high-level point of view - is not present, these are different types of storage. With low-level - same, purely speculative (logical).