diff options
author | 2016-09-25 07:30:03 -0400 | |
---|---|---|
committer | 2016-09-25 07:30:03 -0400 | |
commit | f83fce0c281cb0b13a323860c8995ae84d3fcb4a (patch) | |
tree | fa401e86ac4d839e3d638c8cc00b73623c8b2ee0 /plugins/data/load_dat.lua | |
parent | 5f3bb35b126e1e3323f31a748f6b027c8d866587 (diff) |
Putting try { ... } catch(std::bad_alloc &) { ... } around recently introduced resize() calls
At the very least, I suppose this doesn't hurt; I'd just like to discuss how this should work in the long run.
Also, this blog entry sums up my opinion perfectly: http://christiangarbin.blogspot.com/2013/05/the-futility-of-catching-stdbadalloc.html
Diffstat (limited to 'plugins/data/load_dat.lua')
0 files changed, 0 insertions, 0 deletions