Path: utzoo!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!zaphod.mps.ohio-state.edu!sol.ctr.columbia.edu!emory!utkcs2!ornl.gov!de5
From: de5@ornl.gov (Dave Sill)
Newsgroups: news.software.b
Subject: Re: C-news on DECsystem 5810 under Ultrix 3.1C
Message-ID: <1991Mar15.124555.10361@cs.utk.edu>
Date: 15 Mar 91 12:45:55 GMT
References: <1991Mar13.123949.5826@cs.utk.edu> <1991Mar13.162056.19587@zoo.toronto.edu>
Sender: usenet@cs.utk.edu (USENET News Poster)
Reply-To: Dave Sill <de5@ornl.gov>
Organization: Oak Ridge National Laboratory
Lines: 38

In article <1991Mar13.162056.19587@zoo.toronto.edu>, henry@zoo.toronto.edu (Henry Spencer) writes:
>In article <1991Mar13.123949.5826@cs.utk.edu> Dave Sill <de5@ornl.gov> writes:
>>cc -O -I../include -c string.c
>>(ccom): string.c, line 135: ccom: Internal: wasted space: 2001731410
>>      }
>>      ^
>>Anybody know what the problem is, or if there's a workaround? ...
>
>Read "Values of Logical Operators" in notebook/problems.

Thanks, that was the problem alright.  But...

Even though I read the problems file, and even that section, I made no
connection between the problem described and my symptom.  The only
obvious connection was the mention of Ultrix.  Perhaps if the "Values
of Logical Operators" section included the above error message I would
have caught it.

But this begs a larger question:  If you knew that some systems bombed
on the
 
    *p++ = isascii(c) && isalnum(c);

line, why didn't you just change it to

    *p++ = (isascii(c) && isalnum(c)) ? 1 : 0;?

Is this just a stubborn refusal to "clutter" your code at the expense
of those who have to make it work?  If it is, I think you've made a
terrible mistake.

I've got more C-news (and NNTP) gripes, but they deserve their own
article.

-- 
Dave Sill (de5@ornl.gov)	  It will be a great day when our schools have
Martin Marietta Energy Systems    all the money they need and the Air Force
Workstation Support               has to hold a bake sale to buy a new bomber.