Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!watmath!clyde!burl!ulysses!allegra!mit-eddie!genrad!panda!husc6!harvard!seismo!rochester!ritcv!cci632!ccird1!rb
From: rb@ccird1.UUCP (Rex Ballard)
Newsgroups: net.lang.c
Subject: Additions to C - Entry
Message-ID: <454@ccird1.UUCP>
Date: Fri, 6-Jun-86 18:58:59 EDT
Article-I.D.: ccird1.454
Posted: Fri Jun  6 18:58:59 1986
Date-Received: Sun, 8-Jun-86 06:24:46 EDT
References: <697@bu-cs.UUCP>
Reply-To: rb@ccird1.UUCP (Rex Ballard)
Organization: CCI Rochester Development, Rochester NY
Lines: 19

In article <697@bu-cs.UUCP> bzs@bu-cs.UUCP (Barry Shein) writes:
>
>Re: cpp as a separate pass/program
>
>I wonder out loud how hard it would be to turn CPP into a subroutine,
>change its main() to cpp_main() and set up the call in the main() of ccom,
>and of course figure out a way to get cc to understand that (probably could
>just pass the arg list as a single quoted string and break it up in ccom?)
>

What I would like is some provision for the C compiler to key on
the name of the output program as an alternate entry point.  In
other words, given a frequently used "shell script" that seems
painfully slow, be able to "link" to the executable using a different
C "mainline".  Alternatively, it could key on the first "entry"
lable found.

In this case, the problem is more legal than technical, but
isn't really that ambiuous.