Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!csd4.milw.wisc.edu!lll-winken!uunet!mcvax!nikhefh!t19
From: t19@nikhefh.hep.nl (Geert J v Oldenborgh)
Newsgroups: comp.sys.atari.st
Subject: Folded vs STedi
Keywords: folding editor
Message-ID: <223@nikhefh.hep.nl>
Date: 24 Jul 89 22:42:52 GMT
Organization: Nikhef-H, Amsterdam (the Netherlands).
Lines: 66

I just played around a bit with Folded.

Here are some benchmarks against the other folding editor on the ST,
STedi (version 2.0beta).  They are not quite fair:  STedi is a commercial 
product whereas Folded was given away free, and apologizes for the lack of 
attention paid to speed.  Furthermore, the PC and UNOX versions of STedi are 
still in the beta-test stage only.

Reading a 87.5K file from cache, including start-up time:
	Folded:	14.78 s
	STedi:	 2.22 s

Searching for the string ZZZZ at the end of the file:
	Folded:	 5.6 s
	STedi:	 0.5 s

Scrolling through the entire 3582 line file, using J/shift arrow:
	Folded:	76.4 s
	STedi:	11.4 s

Substitute one char -> one char, 1536 times (m->M):
	Folded:	 6.0 s
	STedi:	 1.5 s

Substitute "delta" -> "lange string" (this forces the line to be moved), 512 
times:
	Folded:	 8.3 s
	STedi:	 0.8 s

Furthermore, I have some questions:	
- How does one go to a specific line and edit it (as in 
  "Error on line 737 of ffdxc0.f: Wrongly nested DO statements")
  (STedi: <Command>[737 opens all folds to get to this line)
- Is there no 'find matching bracket' command?
- The incremental search is quite annoying on a slow line, or even the 
  ST screen, is there a way to turn it off?
- Screen updates are too frequent.

I still do not like its concept of folding-by-indentation or seperate file 
too much.  The info in the file does not look too bad.  Here is a screendump 
of STedi (on UNOX), to prove that fold info in the file can add to readability:

-------------------------------------------------------------------------------
*###[ ffdcs:
        subroutine ffdcs(cs3,ipi12,cy,cz,cdyz,cd2yzz,cdyzzy,cpi,cpiDpj,
     +                                          ii,ns,isoort,ier)
***##*comment:***********************************************************
*  ## declarations:
*  ## check input:
*  #[ normal case:
        if ( isoort(1) .ne. isoort(9) .or. isoort(1) .gt. -10 ) then
            if ( lwrite ) print *,'ffdcs: normal case'
            .
            some Fortran statements
            .
        endif
*  #] normal case:
*  #[ rotated R's:
      .
      rest of program
-------------------------------------------------------------------------------

I hope this helps identifying areas in which Folded can be improved,

	Geert Jan van Oldenborgh
	t19@nikhefh.hep.nl