QUESTION: Format C Code in THINK C 4.0

rapic...@miavx1.acs.muohio.edu

unread,

Sep 22, 1990, 10:57:51 AM9/22/90

to

A question...

I'm sure you have seen how THINK pascal formats you're text.

Well, I like that feature of having keywords in bold and code structures
formatted so you can tell where they are...

Why was this feature taken out of THINK C ?

And...is there anyway I can put it into THINK C.

--
$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$

Rob Pickering

internet: pick...@apsvax.aps.muohio.edu NeXT: pick...@next4.acs.muohio.edu
bitnet : rp1v...@miamiu.bitnet

"One time the police stopped me for speeding, and they said,'Hey, don't
you know that the speed limit is 55 miles per hour?'.
I said,'Yeah, I know...but I wasn't going to be out that long.'"
-Steven Wright

$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$

Phil Shapiro

unread,

Sep 24, 1990, 11:38:58 AM9/24/90

to

In article <2377.2...@miavx1.acs.muohio.edu> rapic...@miavx1.acs.muohio.edu writes:
> A question...
>
> I'm sure you have seen how THINK pascal formats you're text.
>
> Well, I like that feature of having keywords in bold and code structures
> formatted so you can tell where they are...
>
> Why was this feature taken out of THINK C ?
>
> And...is there anyway I can put it into THINK C.

It was never in Think C. Think Pascal formats code because it parses
your code as it is loaded, so the editor 'decodes' the parse tree in
order to display your program. Thus, you get (feature) automatic
formatting and bolding and lose (misfeature?) the ability to
arbitrarily reformat the code as you wish.

You can use Pretty-C (v.1.04) to get nice looking code listings. It's
ftpable from sumex-aim, $25 shareware.

-phil shapiro, symantec tech support
--
Phil Shapiro
ph...@chaos.cs.brandeis.edu

Francis Stracke

unread,

Sep 26, 1990, 5:45:59 PM9/26/90

to

In article <2377.2...@miavx1.acs.muohio.edu> rapic...@miavx1.acs.muohio.edu writes:

>A question...
>
>I'm sure you have seen how THINK pascal formats you're text.
>

>Why was this feature taken out of THINK C ?

THINK Pascal (LSP) is descended from Mac Pascal, the first (2nd?) Mac language.
Mac Pascal originated the pretty-printing; LSP inherited it, apparently to
punish us. LSC is not actually related to LSP; it predates Symantec's
acquisition of the latter (question: anybody know how that came about?). There
was never any pretty-printing in LSC; it wasn't taken out.

>And...is there anyway I can put it into THINK C.

Hahahahahaha...
Why would you want to, anyway? It's kind of nice, but it gets obnoxious.
Especially when you've got a godawful long list of things that you've told it
you want printed horizontally (variables and unit names, for example--either all
on one line or each on its own).

Rich Siegel

unread,

Sep 26, 1990, 10:00:44 PM9/26/90

to

In article <1990Sep26.2...@midway.uchicago.edu> fra...@arthur.uchicago.edu (Francis Stracke) writes:
>THINK Pascal (LSP) is descended from Mac Pascal, the first (2nd?) Mac language.
>Mac Pascal originated the pretty-printing; LSP inherited it, apparently to
>punish us. LSC is not actually related to LSP; it predates Symantec's
>acquisition of the latter (question: anybody know how that came about?). There
>was never any pretty-printing in LSC; it wasn't taken out.

Close, but not quite. :-) Here's the history, in approximate
chronological order:

Macintosh Pascal was the first high-level language implementation
which ran on a Mac.

Macintosh Pascal begat Lightspeed Pascal (trivia question:
in early fliers, what was Lightspeed Pascal called?)

LightspeedC and Lightspeed Pascal were released, within months
of one another.

Lightspeed, Inc., makers of the Lightspeed Color Layout System,
took exception to THINK Technologies' use of the name "Lightspeed"
in the products. As a result, the product names went through a
gradual change:

LightspeedC became THINK's LightspeedC, and then became THINK C.
Lightspeed Pascal became THINK's Lightspeed Pascal, and then
became THINK Pascal.

Neither product was "acquired" separately by Symantec; THINK Technologies,
however, became part of Symantec.

The pretty-printer in THINK Pascal is not an ancillary feature; it's
a direct side-effect of the architecture of the product.

(p.s. Macintosh Pascal, the interpreter, is still alive and kicking.)

R.
Rich Siegel Software Engineer Symantec Languages Group
Internet: sie...@endor.harvard.edu UUCP: ..harvard!endor!siegel

If you have telekinetic powers, raise my hand.

Owen M. Hartnett

unread,

Sep 26, 1990, 11:37:54 PM9/26/90

to

In article <42...@husc6.harvard.edu> sie...@endor.UUCP (Rich Siegel) writes:
> Macintosh Pascal begat Lightspeed Pascal (trivia question:
> in early fliers, what was Lightspeed Pascal called?)

I'm going to take a shot. I could be wrong, but something way in the
back of my head says "QuickSilver."

-Owen

Owen Hartnett o...@cs.brown.edu.CSNET
Brown University Computer Science o...@cs.brown.edu
uunet!brunix!omh
"Don't wait up for me tonight because I won't be home for a month."

Francis Stracke

unread,

Sep 27, 1990, 11:03:09 AM9/27/90

to

First of all: apologies to all I've managed to offend in the past 2 days.
I'll calm down from here on.

In article <42...@husc6.harvard.edu> sie...@endor.UUCP (Rich Siegel) writes:

[My version of the LightSpeed geneology]

> Close, but not quite. :-) Here's the history, in approximate
> chronological order:

[...]

> Macintosh Pascal begat Lightspeed Pascal (trivia question:
> in early fliers, what was Lightspeed Pascal called?)

Thanks for the correction (I was just going by when I saw LSP and LSC appear).
The thing I've been curious about is how this begatting came about.