[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Octave-bug-tracker] [bug #50165] coder.varsize is not ignored
From: |
anonymous |
Subject: |
[Octave-bug-tracker] [bug #50165] coder.varsize is not ignored |
Date: |
Fri, 27 Jan 2017 20:34:24 +0000 (UTC) |
User-agent: |
Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:51.0) Gecko/20100101 Firefox/51.0 |
URL:
<http://savannah.gnu.org/bugs/?50165>
Summary: coder.varsize is not ignored
Project: GNU Octave
Submitted by: None
Submitted on: Fri 27 Jan 2017 08:34:23 PM UTC
Category: Octave Function
Severity: 3 - Normal
Priority: 5 - Normal
Item Group: Matlab Compatibility
Status: None
Assigned to: None
Originator Name: Makhno
Originator Email:
Open/Closed: Open
Discussion Lock: Any
Release: 4.0.0
Operating System: GNU/Linux
_______________________________________________________
Details:
One use of Matlab is the autocoding function. Though it is a travesty, it is
commonly used in the industry I'm in. It produces surprisingly clear, but
horrifically buggy code.
Octave doesn't support autocoding of course, and that's not the problem here.
The problem here is that many scripts that are destined for autocoding but
also are used in regular Matlab have 'coder' references that direct the
autocoder to generate appropriate code. These coder references, like for
example
coder.varsize('some_var',[6,1],[0,1]);
are ignored when regular Matlab is running.
Unfortunately, Octave does not ignore these coder references and stops with an
error. This makes it difficult to produce mutually compatible code.
_______________________________________________________
Reply to this item at:
<http://savannah.gnu.org/bugs/?50165>
_______________________________________________
Message sent via/by Savannah
http://savannah.gnu.org/
- [Octave-bug-tracker] [bug #50165] coder.varsize is not ignored,
anonymous <=