Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!linus!philabs!seismo!harpo!ihnp4!inuxc!pur-ee!uiucdcs!parsec!ctvax!uokvax!emjej
From: emjej@uokvax.UUCP
Newsgroups: net.unix
Subject: pc 'used but never set' query - (nf)
Message-ID: <4741@uiucdcs.UUCP>
Date: Fri, 30-Dec-83 22:47:02 EST
Article-I.D.: uiucdcs.4741
Posted: Fri Dec 30 22:47:02 1983
Date-Received: Fri, 6-Jan-84 01:52:21 EST
Lines: 20

#N:uokvax:6100009:000:808
uokvax!emjej    Dec 27 20:55:00 1983

This isn't *really* a bug, so I'm putting it here: Berkeley's pc
is nice enough to tell me about variables that are used but not
assigned to. This is quite useful, *BUT* the program I'm currently
working on has a fair number of records with fields with the same
names, and n lines of

	field zot is used but never set

is less helpful than I would like. I'd appreciate hearing about whether
it's reasonable (I know that's a vague notion) to give at least one
line # with a usage of said unset field, whether it's reasonable for
one's local system administrator to make such a hack (not that it's
likely I'll ever nag the local folks to do so; they've got enough to
do), and whether Berkeley is likely to ever do so. (Please, no messages
concerning the desirability of such field names...)

						James Jones