Path: news.mathworks.com!not-for-mail
From: <HIDDEN>
Newsgroups: comp.soft-sys.matlab
Subject: Re: Modifying MEX arguments in place?
Date: Fri, 15 Feb 2008 01:31:02 +0000 (UTC)
Organization: Boeing
Lines: 9
Message-ID: <fp2q0m$egn$1@fred.mathworks.com>
References: <fp0fqv$3gd$1@fred.mathworks.com> <muyir0r1v1p.fsf@G99-Boettcher.llan.ll.mit.edu> <fp2ede$j0a$1@fred.mathworks.com>
Reply-To: <HIDDEN>
NNTP-Posting-Host: webapp-03-blr.mathworks.com
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 8bit
X-Trace: fred.mathworks.com 1203039062 14871 172.30.248.38 (15 Feb 2008 01:31:02 GMT)
X-Complaints-To: news@mathworks.com
NNTP-Posting-Date: Fri, 15 Feb 2008 01:31:02 +0000 (UTC)
X-Newsreader: MATLAB Central Newsreader 756104
Xref: news.mathworks.com comp.soft-sys.matlab:451539




Just did a quick check. mxUnshareArray does indeed return 
control to MATLAB (with an out-of-memory error message) if 
there is an out of memory error inside the call. I don't 
know about engine applications yet.

James Tursa