Object in Kotlin loosing it var values?
up vote
0
down vote
favorite
I recently made the transition from iOS/Swift to Androi/Kotlin. I am using a object for encapsulating Analytics functionality (as I did in Swift):
Object Analytics
var connection: AnalyticsConnection? = null
fun sendEvent(name: String)...
init
connection = //allocate here
I heard (one of our Android devs mentioned it) that in the latest version of kotlin the var connection
could actually loose it value at some point spontanically? I find this very weird, is this true? It seams that vars at global scope get cleared out at some point?
android kotlin
add a comment |
up vote
0
down vote
favorite
I recently made the transition from iOS/Swift to Androi/Kotlin. I am using a object for encapsulating Analytics functionality (as I did in Swift):
Object Analytics
var connection: AnalyticsConnection? = null
fun sendEvent(name: String)...
init
connection = //allocate here
I heard (one of our Android devs mentioned it) that in the latest version of kotlin the var connection
could actually loose it value at some point spontanically? I find this very weird, is this true? It seams that vars at global scope get cleared out at some point?
android kotlin
Did it looses its value ?
– Vivek Mishra
Nov 12 at 6:29
No, most likely they were talking about process being killed by the OS (see medium.com/inloopx/… and developer.android.com/guide/components/activities/…). But Kotlin version isn't relevant here.
– Alexey Romanov
Nov 12 at 8:56
add a comment |
up vote
0
down vote
favorite
up vote
0
down vote
favorite
I recently made the transition from iOS/Swift to Androi/Kotlin. I am using a object for encapsulating Analytics functionality (as I did in Swift):
Object Analytics
var connection: AnalyticsConnection? = null
fun sendEvent(name: String)...
init
connection = //allocate here
I heard (one of our Android devs mentioned it) that in the latest version of kotlin the var connection
could actually loose it value at some point spontanically? I find this very weird, is this true? It seams that vars at global scope get cleared out at some point?
android kotlin
I recently made the transition from iOS/Swift to Androi/Kotlin. I am using a object for encapsulating Analytics functionality (as I did in Swift):
Object Analytics
var connection: AnalyticsConnection? = null
fun sendEvent(name: String)...
init
connection = //allocate here
I heard (one of our Android devs mentioned it) that in the latest version of kotlin the var connection
could actually loose it value at some point spontanically? I find this very weird, is this true? It seams that vars at global scope get cleared out at some point?
android kotlin
android kotlin
asked Nov 12 at 6:27
HixField
1,2021921
1,2021921
Did it looses its value ?
– Vivek Mishra
Nov 12 at 6:29
No, most likely they were talking about process being killed by the OS (see medium.com/inloopx/… and developer.android.com/guide/components/activities/…). But Kotlin version isn't relevant here.
– Alexey Romanov
Nov 12 at 8:56
add a comment |
Did it looses its value ?
– Vivek Mishra
Nov 12 at 6:29
No, most likely they were talking about process being killed by the OS (see medium.com/inloopx/… and developer.android.com/guide/components/activities/…). But Kotlin version isn't relevant here.
– Alexey Romanov
Nov 12 at 8:56
Did it looses its value ?
– Vivek Mishra
Nov 12 at 6:29
Did it looses its value ?
– Vivek Mishra
Nov 12 at 6:29
No, most likely they were talking about process being killed by the OS (see medium.com/inloopx/… and developer.android.com/guide/components/activities/…). But Kotlin version isn't relevant here.
– Alexey Romanov
Nov 12 at 8:56
No, most likely they were talking about process being killed by the OS (see medium.com/inloopx/… and developer.android.com/guide/components/activities/…). But Kotlin version isn't relevant here.
– Alexey Romanov
Nov 12 at 8:56
add a comment |
1 Answer
1
active
oldest
votes
up vote
3
down vote
It should not lose the values it contains because when you create a new class as an object you create it as a thread-safe singleton.
Which means unless you directly change the value somewhere else, the value should stay the same as the original value.
That's all in case your application is still alive, in case your application is killed/ destroyed the whole class would also be destroyed with it.
add a comment |
Your Answer
StackExchange.ifUsing("editor", function ()
StackExchange.using("externalEditor", function ()
StackExchange.using("snippets", function ()
StackExchange.snippets.init();
);
);
, "code-snippets");
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "1"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);
else
createEditor();
);
function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);
);
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53256901%2fobject-in-kotlin-loosing-it-var-values%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
3
down vote
It should not lose the values it contains because when you create a new class as an object you create it as a thread-safe singleton.
Which means unless you directly change the value somewhere else, the value should stay the same as the original value.
That's all in case your application is still alive, in case your application is killed/ destroyed the whole class would also be destroyed with it.
add a comment |
up vote
3
down vote
It should not lose the values it contains because when you create a new class as an object you create it as a thread-safe singleton.
Which means unless you directly change the value somewhere else, the value should stay the same as the original value.
That's all in case your application is still alive, in case your application is killed/ destroyed the whole class would also be destroyed with it.
add a comment |
up vote
3
down vote
up vote
3
down vote
It should not lose the values it contains because when you create a new class as an object you create it as a thread-safe singleton.
Which means unless you directly change the value somewhere else, the value should stay the same as the original value.
That's all in case your application is still alive, in case your application is killed/ destroyed the whole class would also be destroyed with it.
It should not lose the values it contains because when you create a new class as an object you create it as a thread-safe singleton.
Which means unless you directly change the value somewhere else, the value should stay the same as the original value.
That's all in case your application is still alive, in case your application is killed/ destroyed the whole class would also be destroyed with it.
edited Nov 12 at 9:52
answered Nov 12 at 6:55
Gil Goldzweig
495414
495414
add a comment |
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53256901%2fobject-in-kotlin-loosing-it-var-values%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Did it looses its value ?
– Vivek Mishra
Nov 12 at 6:29
No, most likely they were talking about process being killed by the OS (see medium.com/inloopx/… and developer.android.com/guide/components/activities/…). But Kotlin version isn't relevant here.
– Alexey Romanov
Nov 12 at 8:56