Path: utzoo!utgpu!watmath!clyde!att!osu-cis!tut.cis.ohio-state.edu!mailrus!ames!pasteur!ucbvax!POLYA.STANFORD.EDU!lipa
From: lipa@POLYA.STANFORD.EDU (William Lipa)
Newsgroups: comp.sys.mac.programmer
Subject: Problems with Think Pascal 2.0
Message-ID: 
Date: 5 Dec 88 02:53:54 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Lines: 33

Well, here we go again. I haven't had any luck getting a response out of the
Think technical support account (singer@harvard.harvard.edu), so I thought I'd
post to the net in the hope that Rich might see my posting. I'd like to
summarize all the problems I've found with version 2.0 of their compiler.

1. Can't print to a LaserWriter SC in any font other than Monaco 12.
2. Occasionally when you Build Code Resource or Build Application, the linker
   will produce an error message "Duplicate File Name", even though you've
   specifically OK'd the overwrite of the previous version in the dialog.
3. The Build Code Resource and Build Application dialogs intermittently set
   the default folder to the root directory of the disk, not the directory
   of your project (which it should be if you double-clicked on the project
   to start the compiler).
4. You can't use the tab key to get from item to item in the Set Project Type
   dialog.
5. The editor still has the problem with leaving little bits of outlined text
   behind when you delete in front of them. For example, if the line looked
   like "normal OUTLINED" and you start backspacing though normal, parts of
   OUTLINED will not move left like they should. LSP 1.0 had this bug!
6. If you ever open LightsBug, whenever you open the project again LightsBug
   will appear, even if you had closed it before closing the project.
7. I had a very strange problem with a simple sorting program I wrote. Any
   attempt to access or change the variables of the program caused a Bus
   Error. The problem did not go away even when I created a whole new project
   to replace the old one. The program didn't access the Toolbox at all.
   However, now the program works fine. Very strange.

I experienced all these problems on a 4 meg Mac II with 8-bit color,
MultiFinder, System 6.0.2, and an internal Apple drive. I hope these problems
can be fixed because they detract from an otherwise great programming
environment!

Bill Lipa