[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Octave-bug-tracker] [bug #39343] mexErrMsgTxt("") does not abort execut
From: |
anonymous |
Subject: |
[Octave-bug-tracker] [bug #39343] mexErrMsgTxt("") does not abort execution of script. |
Date: |
Tue, 25 Jun 2013 18:40:23 +0000 |
User-agent: |
Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:21.0) Gecko/20100101 Firefox/21.0 |
URL:
<http://savannah.gnu.org/bugs/?39343>
Summary: mexErrMsgTxt("") does not abort execution of script.
Project: GNU Octave
Submitted by: None
Submitted on: Tue 25 Jun 2013 06:40:21 PM UTC
Category: Interpreter
Severity: 3 - Normal
Priority: 5 - Normal
Item Group: Matlab Compatibility
Status: None
Assigned to: None
Originator Name: Mario Kleiner
Originator Email: address@hidden
Open/Closed: Open
Discussion Lock: Any
Release: 3.6.4
Operating System: Any
_______________________________________________________
Details:
In the current stable octave version, the mex c-api function mexErrMsgTxt("")
does not return control to the command prompt, as it should if an empty
zero-terminated string "" is passed as argument.
This differs from Matlab's behaviour, where the same call aborts the mex file,
printing an empty error message.
The original bug report #39271 was closed because the same behaviour for the
error('') function is consistent with Matlab's behaviour. However, this is not
true for the mex api.
The problem is easy to work around in my code, and therefore not really
important to me, but i thought i'll file a bug report anyway to the benefit of
other toolkits porting to octave.
Thanks,
-mario
_______________________________________________________
Reply to this item at:
<http://savannah.gnu.org/bugs/?39343>
_______________________________________________
Message sent via/by Savannah
http://savannah.gnu.org/
- [Octave-bug-tracker] [bug #39343] mexErrMsgTxt("") does not abort execution of script.,
anonymous <=