Skip to content
This repository has been archived by the owner on Feb 28, 2018. It is now read-only.

'object = null' instead 'delete object' for deallocation #22

Open
MaxGraey opened this issue Mar 28, 2017 · 6 comments
Open

'object = null' instead 'delete object' for deallocation #22

MaxGraey opened this issue Mar 28, 2017 · 6 comments

Comments

@MaxGraey
Copy link
Contributor

MaxGraey commented Mar 28, 2017

object = null is standard way to signalize for GC to forcing delete object by reference in js.

@MaxGraey MaxGraey changed the title object = null instead delete object for deallocation 'object = null' instead 'delete object' for deallocation Mar 28, 2017
@nidin
Copy link
Contributor

nidin commented Mar 28, 2017

Thats a cool idea. 👍

@nidin nidin added the v1.0.0 label Mar 28, 2017
@nidin nidin added this to the v1.0.0 milestone Mar 28, 2017
@nidin nidin added the ready label Apr 7, 2017
@winksaville
Copy link
Contributor

What is the philosophy for memory management?

My opinion is to keep things simple and only support manual memory management initially (i.e. malloc/free) and if a module doesn't do any malloc/free operations there would be no cost to the module.

@nidin
Copy link
Contributor

nidin commented Apr 12, 2017 via email

@MaxGraey
Copy link
Contributor Author

Has there been any progress in this direction? Unfortunately I'm not too good at parser stuffs, but I think it should not be too difficult

@nidin
Copy link
Contributor

nidin commented Apr 19, 2017

It is doable. I will try it next week.

@MaxGraey
Copy link
Contributor Author

Great!

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

3 participants