Re: missing tests for cast()

[mike sander]

On 14-01-16 01:06 PM, John W. Eaton wrote:
> On 01/16/2014 12:54 PM, Rik wrote:
>
> > This strategy will work just fine, although you will end up with 
> > pages and
> > pages of tests.  You could explore using a for loop and 'eval' to 
> > compact
> > things, or you might just use a script to generate all the required
> > combinations and paste that in to cast.m.
>
> If we are using a script to generate the tests, then it might as well 
> be part of the build process, similar to the way we generate a large 
> number of tests for sparse.
>
> jwe
at least initially i think i will stay away from integrating with the 
build system.  i think i'll be able to condense the tests with arrays & 
looping.   i will look at the tests for sparse as suggested.

thanks.