Hi Olaf, Thanks for clarification of your diff.
> > I see that your changes are not Matlab compatible. Personally, I have no > > interest in maintaining Matlab compatibility, but perhaps others do? > > Yes, maybe some people who need leasqr must write code that runs both > in Octave and Matlab. I could revert all incompatible changes, making > life a bit harder for me ... Note, however, that there is no way (?) > to get the helptext (without copyright/license notice) displayed in > Octave _and_ Matlab without changes to the file (if a > copyright/license notice is present). One could also leave it to the > respective users to make some changes for compatibility, as they would > have to do also with other Octave functions if they have need for > Matlab compatibility. leasqr was originally Matlab compatible because it > came from a Matlab-related repository. I would also strongly argue that we should not brake Matlab compatibility. While I am personally try to stay away from the Matlab beast, I sometimes have to use it since it supported by our cluster maintainers and Octave is not (octave still missing easy parallelism despite the effort of the people in the parallel thread). But I do debug my code in octave, and I don't want to run octave to Matlab converters just because Emacs cannot highlight staff properly. I also would be happy to review your leasqr patches , since I use this function quite often. -- Eugeniy E. Mikhailov ------------------------------------------------------------------------------ Return on Information: Google Enterprise Search pays you back Get the facts. http://p.sf.net/sfu/google-dev2dev _______________________________________________ Octave-dev mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/octave-dev
