2011/12/22 Søren Hauberg <so...@hauberg.org>:
> tor, 22 12 2011 kl. 09:24 -0500, skrev Jordi Gutiérrez Hermoso:
>> On 22 December 2011 07:33, Arno Onken <asn...@asnelt.org> wrote:
>>
>> > Should kmeans be backward compatible with 3.2.4?
>>
>> I don't think it should be. And Søren's fix to replace [~, foo] =
>> bar() with [tmp, foo] = bar() isn't quite equivalent. Although I don't
>> think min does this, a function can know if an output parameter was
>> requested or not and avoid computing it if it wasn't.
>
> I really don't think this type of performance tweaks makes much (if any)
> difference in real life.

No, not in this case, agreed, but I just think that in general
matching Octave-Forge development to the abilities of some packaged
version of Octave isn't the best idea.

There are already plenty of other incompatibilities with current
Octave-Forge packages and the current stable packaging of Octave in
Debian. Without looking any further,

    jordi@Iris:~/coding/vcs/forge-octave$ find -name "*.m" -exec grep
'\[~' {} \; | wc -l
    18

so there are already at least 18 lines in Octave-Forge packages that
won't work in Octave 3.2.4.

Anyways, it is up to Debian to ensure that they package versions of
Octave-Forge that are compatible with the main Octave packaging, and
they do. Users of Debian should use the Debian packaging of
Octave-Forge. Developers who work on Octave-Forge should be expected
to also work with at least the current released version of Octave.

Does this still sound unreasonable?

If I had it my way, we could have Octave-Forge development branches
that matched Octave's branches, so if you really wanted to support an
old version of Octave, you could do so in a separate branch and use
current features of Octave in your main development branch.

- Jordi G. H.

------------------------------------------------------------------------------
Write once. Port to many.
Get the SDK and tools to simplify cross-platform app development. Create 
new or port existing apps to sell to consumers worldwide. Explore the 
Intel AppUpSM program developer opportunity. appdeveloper.intel.com/join
http://p.sf.net/sfu/intel-appdev
_______________________________________________
Octave-dev mailing list
Octave-dev@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/octave-dev

Reply via email to