On 05/21/2011 10:37 PM, David Bateman wrote:
> Getting rid of the short-circuit warnings is easy, as these are just |
> to replace with || and & with && (in code I didn't write btw). Though
> fixing the dispatch warning is going to be a pain. Its easy enough to
> fix this for the m-files, though for the oct-files I have a couple of
> issues. The build process so that the oct-files concerned end up in a
> @gf or @galois directory? And, are classes going to play nicely with an
> autoloaded oct-file, as the oct-files in the comm packages have multiple
> functions in them.
> 
> I started building a replacement for the galois class in the comms
> package entirely in m-files a while back (see the attached files if your
> interested), but suspect some functions, ginv for example, will always
> be better off as oct-files. So, completing, testing and documenting this
> code always seemed more work than it was worth, as the existing code
> worked. I'm still think about what to do for this
> 
> As for the dependencies, there sure is a lot of them now for the
> communications package more than I remember there being. It would be
> better to try and rationalise where certain functions in octave-forge
> are keep so as to reduce the number of dependencies.
> 
> David

I committed a change that should get rid of all of the warning. Its
minimalist in that the new inst/@galois class mostly just calls the old
code, but it allows the dispatch calls to be removed.

I've checked it in-situ in the build directory but would appreciate if
you try and install it and report back. I'll send a version of the
package offline for you to test

D.


------------------------------------------------------------------------------
What Every C/C++ and Fortran developer Should Know!
Read this article and learn how Intel has extended the reach of its 
next-generation tools to help Windows* and Linux* C/C++ and Fortran 
developers boost performance applications - including clusters. 
http://p.sf.net/sfu/intel-dev2devmay
_______________________________________________
Octave-dev mailing list
Octave-dev@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/octave-dev

Reply via email to