I can think of one: speed. The range checking probably is two if statements. If your code manage the range checking (or you are completely sure that no over/underflow may occur) you can disable it to make it faster when you have to access many elements.
Maybe Glide Creme can point out more reasons. *Alejandro Cámara* PhD Student at the GICO <http://www.ucm.es/info/giboucm/> 2010/7/26 Awhan Patnaik <[email protected]> > > Message: 2 > > Date: Thu, 22 Jul 2010 01:37:55 +0200 > > From: glide creme <[email protected]> > > Subject: [Help-gsl] range check ? > > To: [email protected] > > Hi I'm having trouble disabling the range checking in the gsl. > > I guess I'm abit rusty in the cpreprocessor macro world, so if someone > > can elaborate on issue. > > > > gcc -lgsl gsl.c -lgslcblas -DHAVE_INLINE -DGSL_RANGE_CHECK=0 > > > > I still get the > > gsl: ../gsl/gsl_vector_double.h:177: ERROR: index out of range > > > > To: glide creme <[email protected]> > > Cc: [email protected] > > Hello Glide, > > > > I don't have GCC right now but you might want to try using > > > > -UGSL_RANGE_CHECK > > > > instead of > > > > -DGSL_RANGE_CHECK=0 > > > > Best, > > > > Javier > > > > forgive this offtopic but related question. why would anybody want to > disable range checking? i think its a recipe for disaster ... i m > surprised to even find such a facility in gsl. > > _______________________________________________ > Help-gsl mailing list > [email protected] > http://lists.gnu.org/mailman/listinfo/help-gsl > _______________________________________________ Help-gsl mailing list [email protected] http://lists.gnu.org/mailman/listinfo/help-gsl
