Path: csiph.com!v102.xanadu-bbs.net!xanadu-bbs.net!feeder.erje.net!eu.feeder.erje.net!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail From: "Paul E. Bennett" Newsgroups: comp.lang.forth Subject: Asserting Failure Followup-To: comp.lang.forth Date: Thu, 13 Jun 2013 18:20:50 +0100 Organization: Hidecs Consultancy Lines: 21 Message-ID: Reply-To: Paul_E.Bennett@topmail.co.uk Mime-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7Bit X-Trace: individual.net k0WsYmaJ5TVbYVzwcuchuAst1WwQVAbWbrfg6k9TxBUmqhKGnF Cancel-Lock: sha1:Et5lbgJdCXXLoCHzIKL1feJuHSc= Mail-Copies-To: Paul_E.Bennett@topmail.co.uk User-Agent: KNode/0.99.01 Xref: csiph.com comp.lang.forth:23556 The link is an article by Jack Ganssle about using the assert() feature in C programming. I am not advocating we consider these in Forth but thought others might like to see what they do in another language to try and produce correct software. The Forth philosophy of "Crash Hard, Crash often" during development is I think much better but we also need to ensure that the code is inspected for the quieter systematic problems that can creep in. -- ******************************************************************** Paul E. Bennett............... Forth based HIDECS Consultancy Mob: +44 (0)7811-639972 Tel: +44 (0)1235-510979 Going Forth Safely ..... EBA. www.electric-boat-association.org.uk.. ********************************************************************