Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!utgpu!water!watmath!clyde!rutgers!rochester!cornell!batcomputer!pyramid!prls!gardner
From: gardner@prls.UUCP
Newsgroups: comp.sys.mac
Subject: Possible LSC improvements
Message-ID: <6523@prls.UUCP>
Date: Wed, 30-Sep-87 18:53:58 EDT
Article-I.D.: prls.6523
Posted: Wed Sep 30 18:53:58 1987
Date-Received: Sat, 3-Oct-87 02:22:41 EDT
References: <2071@sfsup.UUCP| <170026@acf3.NYU.EDU> <1236@csib.UUCP> <2948@uwmcsd1.UUCP> <12338510906029@KL.SRI.COM> <2907@husc6.UUCP>
Reply-To: gardner@prls.UUCP (Robert Gardner)
Organization: Philips Research Labs, Sunnyvale, California
Lines: 21

A couple of things I'd like to see in LightSpeed C (which I greatly enjoy):

Macros can be tricky. It would sure be nice to have the compiler optionally
generate a file containing the output of the macro pre-processor. This
would help me catch lots of otherwise very obscure bugs.

I get rather annoyed with C at times because it lets me do dumb things
without complaining. Prototypes help, but I think it would be nice to
have a Lint option that would check your project for dumb mistakes (and
machine-dependency, though Mac programmers don't usually worry about that
too much -- what machine are they going to port their programs to?). It
seems that with LSC's projects, a nice implementation of this could be done.
It wouldn't need to be fast, either, since it would probably only be used
after major revisions or when bug-exterminating.

Other ANSI extensions would be nice, such as allowing function definitions
to have the same format as prototypes (for easier copy/pasteing) and
string/name concatenation at compile time. I would guess, though, that
THINK plans on supporting ANSI in full if and when it is finalized.

Robert Gardner