Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!utgpu!water!watmath!clyde!rutgers!husc6!endor!singer
From: singer@endor.UUCP
Newsgroups: comp.sys.mac
Subject: Re: Possible LSC improvements
Message-ID: <2917@husc6.UUCP>
Date: Wed, 31-Dec-69 18:59:59 EDT
Article-I.D.: husc6.2917
Posted: Wed Dec 31 18:59:59 1969
Date-Received: Sat, 3-Oct-87 04:14:49 EDT
References: <2071@sfsup.UUCP| <170026@acf3.NYU.EDU> <1236@csib.UUCP> <2948@uwmcsd1.UUCP> <12338510906029@KL.SRI.COM> <2907@husc6.UUCP> <6523@prls.UUCP>
Sender: news@husc6.UUCP
Reply-To: singer@endor.UUCP (Richard Siegel)
Organization: THINK Technologies, Inc., Bedford, MA
Lines: 46

In article <6523@prls.UUCP> gardner@prls.UUCP (Robert Gardner) writes:
>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.

	The problem here is that there's no preprocessor per se; macro handling
is part of the compiler itself.

>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.

	The trouble with Lint is that it's not a small project, and we
don't have the resources to devote to a Lint at this time. Note that
Lint doesn't require a project file to work; it'll work on any .c file.

>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.

We're looking at these items, and some of them will be present in the next
major release of LightspeedC.

		--Rich


**The opinions stated herein are my own opinions and do not necessarily
represent the policies or opinions of my employer (THINK Technologies, Inc).

Richard M. Siegel
Customer Support Representative
THINK Technologies, Inc.

Uucp: {decvax, ucbvax, sun}!harvard!endor!singer
Internet/Arpanet: singer@harvard.harvard.edu

No one writes programs that work right the first time. If they did,
I'd be out of a job.