News for hackers. Stuff that matters.
Re:Jai Language Primer by CyberDildonics on Saturday February 13, 2016 @10:49AM (#11094366)
> If you suddenly find yourself in a position when you need deallocation for something that is not supposed to be dislocated then I'd rather have it fail with as much noise as possible than have it covered. E.g. I prefer game crashing on out of memory rather soon than going on with thrashing the heap till it crashes 8 hours into the soak test due to the heap fragmentation.

How would this be different?

> I don't know anybody who would agree with this.

It isn't really something to agree on, in one scenario you have options for automation but don't give up anything, in the other scenario you have no ability to use ownership or scope semantics whether you want to or not.

Re:Jai Language Primer by pandaman on Saturday February 13, 2016 @11:59AM (#11094669)
>How would this be different?

In one case it takes 1-15 minutes to reproduce, in other - 8 hours.

>It isn't really something to agree on, in one scenario you have options for automation but don't give up anything, in the other scenario you have no ability to use ownership or scope semantics whether you want to or not.

Judging by your previous question I figure you don't ship games, do you?

Re:Jai Language Primer by CyberDildonics on Saturday February 13, 2016 @12:22PM (#11094743)
I meant how would the error somehow happen more slowly using an STL data structure than in C?

> I figure you don't ship games, do you

No, I only write them, I've found it's a lot easier to let someone else handle the distribution.

Re:Jai Language Primer by pandaman on Saturday February 13, 2016 @12:26PM (#11094765)
>I meant how would the error somehow happen more slowly using an STL data structure than in C?

That I don't know. As I said, I was only talking about deallocation of arrays that were not supposed to be deallocated.