[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Ideas for auto BSX
From: |
Jordi Gutiérrez Hermoso |
Subject: |
Re: Ideas for auto BSX |
Date: |
Wed, 14 Dec 2011 10:28:03 -0500 |
2011/12/14 Judd Storrs <address@hidden>:
> 2011/10/1 Jordi Gutiérrez Hermoso <address@hidden>:
>> As I've said before, I don't see "Matlab compatibility" to be anything
>> more than source compatibility. If it runs in Matlab, it should run in
>> Octave and produce almost the same result (perhaps slight variation in
>> graphics is acceptable, for example). I don't see making everything in
>> Octave working and looking exactly like Matlab to be the goal. We
>> already have lots of other nice Octave-only language features (e.g.
>> being able to define functions interactively without needing a
>> separate file for each or being able to index temporaries), and that's
>> not lack of Matlab compatibility.
>
> One thing that just occurred to me is: does it become much more
> difficult to automatically translate octave code into code that will
> run in matlab?
Octave already has a bunch of code that is difficult to automatically
translate into Matlab. Unwind-protect? Functions defined in script
files as opposed to function files? Generating intermediate variables
when indexing temporaries?
- Jordi G. H.