🚀 go-pugleaf

In article <AC9C151B9668D9B8@sleipner.nts.mh.se>, lars.farm@nts.mh.se (Lars Farm) writes:
> In article <DG010o.LFK@research.att.com>,
> ark@research.att.com (Andrew Koenig) wrote:
> 
> >Again, I think implementations that check the rules at run time are
> >a Good Thing, especialy if you can afford them.  But sometimes you can't.
> 
> In those few cases, I'd turn checking of selectively after testing and
> profiling. That is, I would if I could. It's always off in all my
> compilers:-( Why not reserve a #pragma for this? imho no range check by
> default is a premature optimization.
I recommend to do it the other way: range check on as default and a 
#pragma to switch it off for the 1% of the code which is really time 
critical (see also the posting of James Kanze).

==================================================================
	
       ...     ...	Andreas C. M. Huennebeck
      .    * .    .	Software Engineer
       .   . .   .	Bruker Analytische Messtechnik GmbH
       B R U K E R	D-76287 Rheinstetten, Germany
       .   . .   .	Tel  : 49 (721) 5161-444
      .    * .    .	Fax  : 49 (721) 5161-437
       ...     ...      email: ah@bruker.de		
| MY OPINIONS ARE MY OWN AND DO NOT REPRESENT THOSE OF MY EMPLOYER |
===================================================================