Path: utzoo!utgpu!news-server.csri.toronto.edu!mailrus!iuvax!noose.ecn.purdue.edu!newton.physics.purdue.edu!maxwell.physics.purdue.edu!sho
From: sho@maxwell.physics.purdue.edu (Sho Kuwamoto)
Newsgroups: comp.sys.mac.programmer
Subject: Re: THINK Pascal enhancements I'd like to see...
Keywords: (as long as we're on the subject)
Message-ID: <3358@newton.physics.purdue.edu>
Date: 24 Mar 90 00:10:32 GMT
References: <9960@wpi.wpi.edu> <13270@burdvax.PRC.Unisys.COM> <1990Mar23.181237.27430@spectre.ccsf.caltech.edu>
Sender: news@newton.physics.purdue.edu
Reply-To: sho@maxwell.physics.purdue.edu.UUCP (Sho Kuwamoto)
Organization: Purdue Univ. Physics Dept., W. Lafayette, IN
Lines: 30

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?