Path: utzoo!mnetor!uunet!husc6!bloom-beacon!mit-eddie!bbn!diamond.bbn.com!mlandau
From: mlandau@bbn.com (Matt Landau)
Newsgroups: comp.lang.c
Subject: Re: C run-time checking
Message-ID: <10725@jade.BBN.COM>
Date: 15 Mar 88 17:00:43 GMT
References: <763@uvm-gen.UUCP> <10651@mimsy.UUCP>
Reply-To: mlandau@bbn.com (Matt Landau)
Organization: BBN Laboratories Incorporated, Cambridge, MA
Lines: 26
Keywords: C arrays pointers run-time-checking

In comp.lang.c (<10651@mimsy.UUCP>), chris@mimsy.UUCP (Chris Torek) writes:
>I have heard of two such compilers; one is called Safe-C and I cannot
>recall the name of the other.  For some reason this is tied in with
>a memory of a C interpreter that can dynamically either interpret or
>compile code: a handy thing to have if you ever write buggy code :-) .

That would be Saber-C, from Saber Software in Cambridge MA.  I've been
using Saber for a while now, and it's a really slick piece of work, not
to mention *very* useful for tracking down a fairly obscure class of
bugs (trashing random memory due to wild pointers).

I've found it reasonably fast and fairly convenient to use (and getting
better with each release).  It's been absolutely wonderful to be able to
test and debug new code in an interpretive environment, without having
to write test drivers, recompile constantly, etc.

Equally important, the folks at Saber seem really concerned with learning 
what we still perceive as problems in the system and fixing them.

DISCLAIMER: These are my opinions, not those of BBN or any of its 
	    subsidiaries.  I have no professional association with
	    Saber other than as a reasonably happy user who once in
	    a while gets to beta test new versions.
--
 Matt Landau			Waiting for a flash of enlightenment
 mlandau@bbn.com			  in all this blood and thunder