Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!utgpu!water!watmath!clyde!rutgers!husc6!necntc!ames!ucbcad!ucbvax!dewey.soe.berkeley.edu!oster
From: oster@dewey.soe.berkeley.edu.UUCP
Newsgroups: comp.sys.mac
Subject: Re: Possible LSC improvements
Message-ID: <21094@ucbvax.BERKELEY.EDU>
Date: Fri, 2-Oct-87 16:36:33 EDT
Article-I.D.: ucbvax.21094
Posted: Fri Oct  2 16:36:33 1987
Date-Received: Sat, 3-Oct-87 10:26:18 EDT
References: <2071@sfsup.UUCP| <170026@acf3.NYU.EDU>
Sender: usenet@ucbvax.BERKELEY.EDU
Reply-To: oster@dewey.soe.berkeley.edu.UUCP (David Phillip Oster)
Organization: School of Education, UC-Berkeley
Lines: 52
Keywords: edit font memory

In article <367@cogen.UUCP> alen@cogen.UUCP (Alen Shapiro) writes:
>I find it annoying that after a R(un command
>(and subsequent exit from my application) my carefully set up
>edit windows and cursor locations within them are lost (on return
>to LSC).

An easy way to do this is:
1.) if you have the recently posted WDEF 2 (multi-finder compatibility
patch installed in your working copy of LightSpeed C, then throw it away
and make a new copy of your master.

2.) Start Switcher (I use version 5.5, available from user's groups and
APDA)

3.) Use Switcher's "Get Info" command to find out how much memory you've
got.

4.) Use Switcher's "Configure and Install" command to configure LightSpeed
C to use almost all the free memory (I give mine 750k on a 1 meg machine.
Performance is improved by giving it at least a small RAM Cache (On the
control panel.))

5.) Now, when you run a program under test and exit it, LSC comes back much
faster, with all your open files, scroll positions, and cursor positions
intact.

6.) For conveninence, I create a "Switcher Set" document for each of
my projects that when you double click on it:
  a.) Starts Switcher
  b.) starts LSC
  c.) opens the project.

I double click on these instead of on the project documents.

You can even examine the source code while the program is running. Remember
though, you must open all the files you are going to want to look at 
before you hit the Run command.
You can switch out of the running-program-under-test and back to LightSpeed
C, but you must be careful not to open any more files until you quit
the running-program-under-test.  This flaw is because LSC gives up a little
too much memory to the running-program-under-test.  You get back to the
program-under-test with <command>-R (the resume command.)

If you write applications or DAs in LSC, this method of development is
great for your edit-compile-test cycle.  I use this scheme all the time
under System 4.1. I test very frequently because it is so fast and I don't
lose my place in my source code.


--- David Phillip Oster            --Thanks to THINK Inc. (now a subsidiary)
Arpa: oster@dewey.soe.berkeley.edu --for a truly great product.
Uucp: {uwvax,decvax,ihnp4}!ucbvax!oster%dewey.soe.berkeley.edu