Jaroslav Hajek wrote: > Alternatively, you can check `ver' and use the new code if ver is >= > 3.2.0, or you can even check directly for the feature using `try'. The > advantage is that you will actually get the new functionality. The old > code may be removed at some point in the future. Your choice, of > course.
Or just assume that the next octave-forge release will be for 3.2 :-) At least that was the aim, though 3.2 is seeming further away at the moment. D. -- David Bateman [EMAIL PROTECTED] 35 rue Gambetta +33 1 46 04 02 18 (Home) 92100 Boulogne-Billancourt FRANCE +33 6 72 01 06 33 (Mob) ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ Octave-dev mailing list Octave-dev@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/octave-dev
