02-20-2018, 04:29 PM
By operating on values, I meant exactly changing them. It's what could cause crashes, yes.
Maybe adding synchronization somewhere would fix this? Though, I'm not sure about static-ness of Camps itself (I mean, Camps.Camps) - it's not declared as static, so if there are multiple instances, 'Camps' array is not shared anyway(?).
As for static methods, the documentation (SatCom) of 'static' states that I can make static methods. :c But it seems I can't. And I would need to access them without the instance anyway, so, well, it's stupid.
I wanted to make something like this - Wikipedia on singletons.
Single instance, no way of creating other instances (private constructor), static getter to get that single instance... Because you first thought it's about static things.
Maybe adding synchronization somewhere would fix this? Though, I'm not sure about static-ness of Camps itself (I mean, Camps.Camps) - it's not declared as static, so if there are multiple instances, 'Camps' array is not shared anyway(?).
As for static methods, the documentation (SatCom) of 'static' states that I can make static methods. :c But it seems I can't. And I would need to access them without the instance anyway, so, well, it's stupid.
I wanted to make something like this - Wikipedia on singletons.
Single instance, no way of creating other instances (private constructor), static getter to get that single instance... Because you first thought it's about static things.