octave-bug-tracker
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Octave-bug-tracker] [bug #39984] MATLAB's mex accepts options not in Oc


From: anonymous
Subject: [Octave-bug-tracker] [bug #39984] MATLAB's mex accepts options not in Octave's version
Date: Sun, 08 Sep 2013 00:54:36 +0000
User-agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/29.0.1547.62 Safari/537.36

URL:
  <http://savannah.gnu.org/bugs/?39984>

                 Summary: MATLAB's mex accepts options not in Octave's version
                 Project: GNU Octave
            Submitted by: None
            Submitted on: Sun 08 Sep 2013 12:54:35 AM UTC
                Category: None
                Severity: 3 - Normal
                Priority: 5 - Normal
              Item Group: Matlab Compatibility
                  Status: None
             Assigned to: None
         Originator Name: Warren
        Originator Email: 
             Open/Closed: Open
         Discussion Lock: Any
                 Release: other
        Operating System: GNU/Linux

    _______________________________________________________

Details:

MATLAB's "mex" command accepts a "-O" option to turn on optimization:
    www.mathworks.com/help/matlab/ref/mex.html .
Octave does not accept this option, e.g.

    $ octave --traditional --no-gui --norc -q --eval "mex -O hi.c"
    mkoctfile: unrecognized argument -O
    >> 

MATLAB mex's "-largeArrayDims" option has a similar problem: it is allowed but
is treated as a linker directive. There's a similar problem with MATLAB's
"-output" option: Octave requires "--output" instead. Maybe octave should
accept these options but print a warning that they're ignored?

IMHO compatibility is far more important than avoiding the sin of accepting
options that violate the convention that multiple character options require
two dashes.

I'm using Octave version 3.7.1+. IIRC I built this myself from source around a
year ago. I can reproduce with another version if needed.




    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/bugs/?39984>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/




reply via email to

[Prev in Thread] Current Thread [Next in Thread]