[comp.sys.mac.programmer] THINK Pascal enhancements I'd like to see...

jayvana@wpi.wpi.edu (Jay van Achterberg) (03/21/90)

I use THINK Pascal for writing programming assignments at college, and
use Microsoft Word to write up my description/analysis of the program.

Since Word has some powerful page layout-type abilities, I often want to
include my source code from THINK Pascal directly into the write up, to make
everything look really nice. The problem with this is that I lose the pretty
bold Pascal keywords that I would get if I printed directly from THINK
Pascal.

The enhancement I have in mind is to give THINK Pascal the ability to save
the program as a formatted MacWrite or RTF document. Or at least give it
the ability to save the fancy formatting when copying to the clipboard.

If this ability exists in the new version 3.0, let me know and I think I
might order out for the upgrade tomorrow!

				-Jay (jayvana@wpi.wpi.edu, jayvana@wpi.bitnet)

dave@PRC.Unisys.COM (David Lee Matuszek) (03/24/90)

In article <9960@wpi.wpi.edu> jayvana@wpi.wpi.edu (Jay van Achterberg) writes:

>The enhancement I have in mind is to give THINK Pascal the ability to save
>the program as a formatted MacWrite or RTF document. Or at least give it
>the ability to save the fancy formatting when copying to the clipboard.

I second that.
-- Dave Matuszek (dave@prc.unisys.com)
-- Unisys Corp. / Paoli Research Center / PO Box 517 / Paoli PA  19301
-- Any resemblance between my opinions and those of my employer is improbable.
  << "Next time, Jack, write a goddamned memo!"  >>

palmer@tybalt.caltech.edu (David Palmer) (03/24/90)

What I'd like to see in the Think C editor is the ability to 'hide'
nested code.  This would be done in a manner similar to an outline processor.
When you open up a file, each procedure is represented
by just its definition.  Double click on that, and you get something like

void foo(int bar, double *prime)
{
    int i;
    char *text;
    for (i = 0 ; text[i] != '\0' ; i++) {
    }
}

Clicking on the 'for' reveals its contents, etc.

Of course, I only want it if it can be fully configured for different 
indenting styles etc., and if it can be turned off.

I have heard that the editor which is used for Occam on transputers does this,
but I have never seen this.

--
		David Palmer
		palmer@tybalt.caltech.edu
		...rutgers!cit-vax!tybalt.caltech.edu!palmer
       Meanwhile, on eng.string.floss, the waxed vs. unwaxed flamewar continues.

sho@maxwell.physics.purdue.edu (Sho Kuwamoto) (03/24/90)

In article <1990Mar23.181237.27430@spectre.ccsf.caltech.edu> palmer@tybalt.caltech.edu (David Palmer) writes:
>
>What I'd like to see in the Think C editor is the ability to 'hide'
>nested code.  This would be done in a manner similar to an outline processor.

I would only endorse this if it would print comments right after the
open brace even when the code inside is hidden:

    for(i=0; i<10; i++){
        /* calculate flarg coefficients */
        ...
        flarg[i] += blah*flack;
    }

goes to:
    for(i=0; i<10; i++){
        /* calculate flarg coefficients */
    }

Even so, I could see this as being extremely disorienting.  There
would have to be some visual cue which would let you know that there
is hidden text.  Perhaps the comment could be put in italics.  If
there is no comment, a default, like /* code hidden */ could be placed
there, again in italics.  As it is, I can think of more standard
improvements needed in the THINK C editor, like split panes, macros,
etc.  Come to think of it, what I want is GNU Emacs, dammit.

-Sho
--
sho@physics.purdue.edu  <<-- anyone willing to port it?

philip@Kermit.Stanford.EDU (Philip Machanick) (03/24/90)

In article <1990Mar23.181237.27430@spectre.ccsf.caltech.edu>,
palmer@tybalt.caltech.edu (David Palmer) writes:
> 
> What I'd like to see in the Think C editor is the ability to 'hide'
> nested code.  This would be done in a manner similar to an outline processor.
> When you open up a file, each procedure is represented
> by just its definition.  Double click on that, and you get something like
> 
> void foo(int bar, double *prime)
> {
>     int i;
>     char *text;
>     for (i = 0 ; text[i] != '\0' ; i++) {
>     }
> }
> 
> Clicking on the 'for' reveals its contents, etc.
> 
> Of course, I only want it if it can be fully configured for different 
> indenting styles etc., and if it can be turned off.
> 
> I have heard that the editor which is used for Occam on transputers
does this,
> but I have never seen this.
> 
It's called the folding editor - a great idea. The whole system is built up
hierarchically like this, including files and directories. Unfortunately,
the detailed implementation isn't so hot, and it's a real pain to use. The
system is called TDS, for Transputer Development System, which I pronounce
as te-de-us. I think a better improvement in the Mac context would be
paned windows, as in MS Word, to allow you to see a function definition as
well as edit the place it's being used.

Philip Machanick
philip@pescadero.stanford.edu

lsr@Apple.COM (Larry Rosenstein) (03/27/90)

In article <1990Mar23.181237.27430@spectre.ccsf.caltech.edu> 
palmer@tybalt.caltech.edu (David Palmer) writes:
>What I'd like to see in the Think C editor is the ability to 'hide'
>nested code.  This would be done in a manner similar to an outline 
processor.

>I have heard that the editor which is used for Occam on transputers does 
this,
>but I have never seen this.

The Pascal GENIE from Carengie Mellon allows you to elide any syntactic 
construct.  When a construct is elided it is replaces with an ellipsis, 
and double-clicking it reveals the original code.  I suspect that this is 
a common feature in structured editors.

Larry Rosenstein, Apple Computer, Inc.
Object Specialist

Internet: lsr@Apple.com   UUCP: {nsc, sun}!apple!lsr
AppleLink: Rosenstein1