Hi Olaf,

> > 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.
> 
> That puts it a bit hard. Please consider that modifying Emacs' Octave
> mode to support Matlab syntax would be a considerable additional
> effort, and that writing Matlab compatible Octave code is also some
> additional effort.
Thank you for trying to keep Matlab compatibility. Looks like you do it
just for me. It seems that ecen current SVN version of leasqr has some
issues with Matlab, it complains about single % at th line. I will try
to resolve it once we converge on Octave version.

Is your patch against latest SVN version of optim package? Somehow it
refuses to apply.

By the way it looks like you implemented are bounding version of leasqr,
thanks a lot. I was about  reinventing the will since I needed it, but
the SVN already has it.

Overall I do not see anything wrong with your patch. 



-- 
Eugeniy E. Mikhailov


------------------------------------------------------------------------------
This SF.Net email is sponsored by the Verizon Developer Community
Take advantage of Verizon's best-in-class app development support
A streamlined, 14 day to market process makes app distribution fast and easy
Join now and get one step closer to millions of Verizon customers
http://p.sf.net/sfu/verizon-dev2dev 
_______________________________________________
Octave-dev mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/octave-dev

Reply via email to