[Top][All Lists]

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

[Octave-bug-tracker] [bug #41112] Octave-Symbolic function naming

From: anonymous
Subject: [Octave-bug-tracker] [bug #41112] Octave-Symbolic function naming
Date: Sun, 05 Jan 2014 19:12:08 +0000
User-agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:26.0) Gecko/20100101 Firefox/26.0


                 Summary: Octave-Symbolic function naming
                 Project: GNU Octave
            Submitted by: None
            Submitted on: Sun 05 Jan 2014 07:12:07 PM UTC
                Category: Octave Forge Package
                Severity: 3 - Normal
                Priority: 5 - Normal
              Item Group: Matlab Compatibility
                  Status: None
             Assigned to: None
         Originator Name: Swizzla Kalongie
        Originator Email: address@hidden
             Open/Closed: Open
         Discussion Lock: Any
                 Release: 3.6.4
        Operating System: GNU/Linux



Dear Developers,

First off I would like to say:
Thank you for your hard work on octave. I love it. It has been a tremendous
asset for me as a student. I refuse to crack a copy of matlab just to do my
homework. I wish the school would just use octave instead! GNU FOREVER!

About the BUG that I'd like to report.
some symbolic functions need their names adjusted for case sensitivity.see the
situation below:

I was trying to do an assignment that required me to use symbolic
computations. Normally I just learn the MATLAB syntax in class and write my
octave scripts as such. However there is a nasty difference that I only
spotted by accident: in matlab, cos, cosh and the other functions are the same
for both numerical and symbolic operations. however to do a symbolic y =
cos(x); in octave, you must enter the function name with a capital letter, i.e
y = Cos(x) to get the symbolic cosine function.

I think the symbolic function should be merged in with the standard cos
function. Maybe cos() could use type checking of the function arguments to
determine whether the input type is a symbolic and then call the symbolic
Cos() from the octave-symbolic package. If not installed maybe cos() could
throw an error about the missing symbolic Cos() from the symbolic package. I'm
not an expert, but it actually doesn't sound like too much to do.

How about it? Does my suggestion make sense? I understand octave is NOT
matlab, but compatibility certainly can help encourage adoption.

Thanks Guys! Keep up the good work!
I can't wait to use the GUI when it goes stable.



Reply to this item at:


  Message sent via/by Savannah

reply via email to

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