Comment 4 for bug 461230

I think raising just MemoryError is equally sound, and it is far easier to implement because the std::bad_alloc -> MemoryError translation is built-in. A patch is uploaded. I'm not entirely sure that everything inside Octave is properly cleaned up when std::bad_alloc escapes out of feval or eval_string, but that's better left to Octave itself.
best regards