Path: utzoo!utgpu!news-server.csri.toronto.edu!clyde.concordia.ca!uunet!wuarchive!psuvax1!psuvm!cxt105
From: CXT105@psuvm.psu.edu (Christopher Tate)
Newsgroups: comp.sys.mac.programmer
Subject: Re: Wishlist for THINK _C_ (4.1 ? 5.0 ?)
Summary: If you cannot stand the spoon upright, the coffee is too weak.
Message-ID: <90083.132800CXT105@psuvm.psu.edu>
Date: 24 Mar 90 18:28:00 GMT
References: <3192@draken.nada.kth.se> <2274@cbnewsk.ATT.COM>
 <3200@draken.nada.kth.se>
Reply-To: cxt105@psuvm.psu.edu
Organization: Penn State University
Lines: 49

While we're coming up with a wish list, how about....

1)   A way to toggle 6888x code generation within the source.  It would make
     it so easy to write programs that could be run with any coprocessor
     configuration if you could do something like:

          if (foundCoprocessor) {
               #define _6888x_
               /* use the coprocessor for this code */
               #undef _6888x_
          }
          else {
               /* do the same thing using SANE */
          }

2)   A way to search-and-replace in multiple files at once that are *not*
     in the current project.  I don't know how many times I've wanted to
     do this....

3)   A mechanism that would allow me to keep code in one library at a
     time.  It seems ludicrous to store the code for the ANSI library
     in every project that I'm currently working on -- the disk space
     really adds up, especially on floppies.  Why can't the project just
     contain the information about where to find the code, instead of
     having to copy it into itself?

4)   (This one is a pet peeve, since I got burned by it recently)  The rules
     that THINK C uses for finding the resource file associated with a
     project are different from the rules it uses to find source files.
     For example, you can put your source files into a folder called
     (project_name), and the compiler will find them, but it will not find
     the project_name.rsrc file if it's in that same folder.  I'd like to
     see C use the same rules for finding .rsrc files as it uses for finding
     source code.


Rich, I hope you can pass some of these along.  I realize that 1) is an
extension to C, and therefore suspect, but it'd make things awfully nice.
Another possibility would be for the compiler to generate code to detect the
coprocessor automatically at runtime, and then use the appropriate libraries.
Admittedly, it makes your code quite a bit bigger, but those of us who can't
handle 68881 programming might find it quite convenient....

-------
Christopher Tate                   | "Mr. Churchill, you're drunk!"
                                   |
cxt105@psuvm.psu.edu               | "Yes madam, and you are ugly.  In the
{...}!psuvax1!psuvm.bitnet!cxt105  |  morning, however, I shall be sober."
cxt105@psuvm.bitnet                |