http://h2co3.org
Yes, exactly. So this should probably be decided early.
in the sense that an object is deallocated as soon as all pointers to it cease to exist.
I can remove that option at any time, if it turns out to be an important enough issue :)
Exactly, Sparkling uses reference counting, and one of the major TODOs is the introduction of weak references in order to address the issue of cycles.
No problem – documentation may still be somewhat incomplete at some places, sorry for that.
Hi, author here. Sparkling does have a modulo operator, it's spelled '%', just as in C (in fact, it maps directly to C's % operator).
Why the hell would you even report something as a bug when the code that causes the crash has undefined behavior? Why do you expect UB to work? Seriously… just… WHY?
Update: This is no longer working: https://imgur.com/uT1fCRT
Yes, exactly. So this should probably be decided early.
in the sense that an object is deallocated as soon as all pointers to it cease to exist.
I can remove that option at any time, if it turns out to be an important enough issue :)
Exactly, Sparkling uses reference counting, and one of the major TODOs is the introduction of weak references in order to address the issue of cycles.
No problem – documentation may still be somewhat incomplete at some places, sorry for that.
Hi, author here. Sparkling does have a modulo operator, it's spelled '%', just as in C (in fact, it maps directly to C's % operator).
Why the hell would you even report something as a bug when the code that causes the crash has undefined behavior? Why do you expect UB to work? Seriously… just… WHY?
Update: This is no longer working: https://imgur.com/uT1fCRT