I think you need to say std::min and ensure that the two arguments have the same type.

If I could eliminate the use of CamelCase for the type names, I would.  I would prefer to avoid adding any more.

Sorry, I never finished reading your comments (or if I did I forgot).  I was too concerned with the first part to get through the rest.

If I don't include "min" myself, then I get:

corefcn/find.cc: In function 'octave_idx_type min_with_nnz(const PermMatrix&, octave_idx_type)':
corefcn/find.cc:220:39: error: call of overloaded 'min(octave_idx_type&, octave_idx_type&)' is ambiguous
corefcn/find.cc:220:39: note: candidates are:
../liboctave/array/chNDArray.h:108:31: note: charNDArray min(char, const charNDArray&)
../liboctave/array/chNDArray.h:109:31: note: charNDArray min(const charNDArray&, char)
../liboctave/array/chNDArray.h:110:31: note: charNDArray min(const charNDArray&, const charNDArray&)

If I explicitly specify the type (ie min<octave_idx_type>(a,b)), I get:
corefcn/find.cc: In function 'octave_idx_type min_with_nnz(const Sparse<T>&, octave_idx_type)':
corefcn/find.cc:211:31: error: expected primary-expression before '>' token

#include <algorithm> doesn't seem to fix it.

I can't find anywhere I used CamelCase (except ItType, but I don't think you're referring to that.  It's a type parameter.  It acts like a type like PermMatrix and FloatNDArray etc. which all use CamelCase as far as I can tell)

Since the extra outputs were undocumented and I couldn't find any uses in Octave or Octave Forge, I suppose it would be OK to simply remove them instead of deprecating, warning, then deleting a few releases from now.

I'm not convinced that the additional fourth input argument is needed.  Reshaping is cheap, and Matlab doesn't have this option, does it?  Other functions don't have this option, so why should find?

Could you please separate the addition of the fourth argument from the other patch and submit two separate patches?

It would also be helpful if you could follow the prevailing coding style (primarily the GNU coding style, plus there are a few other tips here: http://www.gnu.org/software/octave/doc/interpreter/C_002b_002b-Sources.html#C_002b_002b-Sources).  We also try to avoid CamelCase.

I think the reason that you didn't find a "min" function in the Octave sources is because there is one in the C++ standard library, defined in <algorithm>.  Is there some reason that won't work in this context?

I cleaned up the "find" function adding templates to channel all calls to 'find' for all types into the same template function.

As a side-effect, this fixes the following matlab/full-matrix incompatibility:
octave:3> a = sparse(0,0);
octave:4> size(find(a))
ans =

1. 1

(Matlab and full matrices give 0 0)

Additionally I added a fourth parameter to specify the desired dimension of the output vectors:
octave:3> a = eye(3);
octave:4> [i,j,v] = find(a,Inf,"first",2)
i =

1 2 3

j =

1 2 3

v =

1 1 1

Could someone please look over my changes?

Thanks