Path: utzoo!mnetor!uunet!lll-winken!lll-lcc!ames!pasteur!agate!ig!uwmcsd1!bbn!rochester!PT.CS.CMU.EDU!andrew.cmu.edu!rs4u+
From: rs4u+@andrew.cmu.edu (Richard Siegel)
Newsgroups: comp.sys.mac.programmer
Subject: Lightspeed Pascal Editor & Syntax errors
Message-ID: <4W94bMy00XoHAJg1RL@andrew.cmu.edu>
Date: 25 Feb 88 16:05:44 GMT
Organization: Carnegie Mellon University
Lines: 28


"(ie. cutting out a section of code may cause an immediate syntax error, if 
your cut creates an invalid program...)

This is most misleading; you should use the program before you start making 
statements like this, please.

What happens generally in the Lightspeed Pascal editor is that when you type a 
semicolon, Return, or Enter key, a bit of magic (which I can't discuss) 
happens, a side effect of which is that the pretty-printer indents your code, 
boldfaces keywords, spaces out expressions so they're readable, and most 
importantly, OUTLINES QUESTIONABLE SYNTAX. Lightspeed Pascal will NOT give an 
error message until you actually try to compile the source, either by doing a 
build or go command; you can also syntax-check the entire source file with a 
"Check" command. Syntactic and semantic errors are posted during compilation, 
*not* during editing.

A cut command may or may not cause this magic to be done, depending on whether 
you delete more than one line. A Paste will *definitely* reformat your code.

>WHEN is 3.0 coming?  Real Soon Now?  Rich?

	Franlkly, folks, I'm getting a bit tired of answering this one. I know that 
inquiring minds want to know. I want to know. What I have said on the net many 
many times, and what I will not say again until I know more, is that I do not 
know the exact release date. It's not far off (i.e. RSN) but I do not have an 
exact date.

Read the posts.