RAS> Date: Wed, 29 Jan 2003 08:18:45 -0500 RAS> From: Richard A Steenbergen RAS> Possibly that bounds checking is an incredible cpu suck, If you check before each byte. Checking for sufficient space first ("is there room for a 245-byte string?") is much faster. Besides, looking at all the bloated code using indirect function calls[*] and crappy code using poor algorithms... is speed really a concern? [*] Try profiling indirect function calls on x86, especially newer cores. Such instructions carry a stiff penalty... but there's no shortage of virtual functions in certain software. (Think: OWL and MFC libraries.) Eddy -- Brotsman & Dreger, Inc. - EverQuick Internet Division Bandwidth, consulting, e-commerce, hosting, and network building Phone: +1 (785) 865-5885 Lawrence and [inter]national Phone: +1 (316) 794-8922 Wichita ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Date: Mon, 21 May 2001 11:23:58 +0000 (GMT) From: A Trap <blacklist@brics.com> To: blacklist@brics.com Subject: Please ignore this portion of my mail signature. These last few lines are a trap for address-harvesting spambots. Do NOT send mail to <blacklist@brics.com>, or you are likely to be blocked.