If you don't explicitly check for zero before attempting a divide (on PC's etc) the hardware / FPU will generate the exception, I don't think it something specific to Borland C++
Ian
It might be a quirk of the Borland compiler - I remember that it set
floating-point overflows etc to be exceptions by default.
steve d.
--
Sorry for the Delphi attached garbage that follows.
**************************************************************************************** Note: If the reader of this message is not the intended recipient, or an employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by replying to the message and deleting it from your computer. Thank you. ****************************************************************************************
-----
No virus found in this message.
Checked by AVG - www.avg.com
Version: 10.0.1204 / Virus Database: 1497/3493 - Release Date: 03/09/11