Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!watmath!clyde!burl!ulysses!mhuxr!mhuxn!mhuxm!mhuxf!mhuxi!mhuhk!mhuxt!houxm!ihnp4!bentley!kwh
From: kwh@bentley.UUCP (KW Heuer)
Newsgroups: net.lang.c
Subject: Re: expression, expression;
Message-ID: <854@bentley.UUCP>
Date: Mon, 26-May-86 14:47:36 EDT
Article-I.D.: bentley.854
Posted: Mon May 26 14:47:36 1986
Date-Received: Wed, 28-May-86 01:49:20 EDT
References: <892@ttrdc.UUCP>
Organization: AT&T Bell Laboratories, Liberty Corner
Lines: 15

In article <892@ttrdc.UUCP> ttrdc!levy (Dan Levy) writes:
>I think there may be at least one good reason NOT to do this ...: for
>debugging.  If you have code which is giving mysterious core dump problems,
>Murphy's law says sdb or adb will show the problem occurring on a line with
>multiple statements on it ...

Well, what *I* do is look at the *instruction* where it bombed, rather than
the statement.  Of course, for less sophisticated users (or when using a
too-smart debugger that won't disassemble) that may not be an option.  This
brings up an interesting question, though.  Given that the language is
almost completely free-format, why should a debugger be line-oriented rather
than statement- or expression-oriented?  (Probable answer: it's trivial to
"point to" a line.)

Karl W. Z. Heuer (ihnp4!bentley!kwh), The Walking Lint