{"id":4577,"date":"2022-08-23T10:44:21","date_gmt":"2022-08-23T05:14:21","guid":{"rendered":"https:\/\/jassweb.com\/solved\/solved-why-arent-all-the-variable-in-cpp-file-in-the-h-file-closed\/"},"modified":"2022-08-23T10:44:21","modified_gmt":"2022-08-23T05:14:21","slug":"solved-why-arent-all-the-variable-in-cpp-file-in-the-h-file-closed","status":"publish","type":"post","link":"https:\/\/jassweb.com\/solved\/solved-why-arent-all-the-variable-in-cpp-file-in-the-h-file-closed\/","title":{"rendered":"[Solved] Why aren’t all the variable in .cpp file in the .h file? [closed]"},"content":{"rendered":"

[ad_1]
\n<\/p>\n

\n
\n
<\/div>\n
\n
\n

The purpose of this tutorial you pointed out is to create the class AFloatingActor<\/code>, which can then be instantiated. The RunningTime<\/code>variable is part of the interface of the class and since it is defined as public<\/p>\n

public:\n    float RunningTime;\n<\/code><\/pre>\n
it can be accessed outside the class (look at public\/private class members and methods). <\/p>\n
Opposed to that, the FVector NewLocation<\/code> and  float DeltaHeight<\/code> are local variables used only in the method AFloatingActor::Tick<\/code>. Because they are used only in this member (function) and nowhere else in the class neither they are part of the class interface, there is no need for them to be class variables. <\/p>\n
If they would be in the .h file (therefore a class variable) then they would be created when the class is instantiated and kept alive as long as the class is. But there is no need for that, therefore they are created when AFloatingActor::Tick<\/code> is called, they do their part and then get destroyed since they are local variables of that method. <\/p>\n
This is also the answer for your second question “What is special about data in the .h files?”.<\/p>\n
To sum it up:
\nIn the .h file of a class you write the class interface. It consist of <\/p>\n