Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!linus!decvax!harpo!eagle!mhuxl!ihnp4!inuxc!pur-ee!uiucdcs!parsec!ctvax!uokvax!andree
From: andree@uokvax.UUCP
Newsgroups: net.lang
Subject: Re: Forced Commenting - (nf)
Message-ID: <4863@uiucdcs.UUCP>
Date: Tue, 10-Jan-84 22:58:15 EST
Article-I.D.: uiucdcs.4863
Posted: Tue Jan 10 22:58:15 1984
Date-Received: Sun, 15-Jan-84 01:09:04 EST
Lines: 24

#R:houxj:-31900:uokvax:9000016:000:1049
uokvax!andree    Jan  9 21:02:00 1984

Yes, I have noticed the problem of screens (and printers) being to
narrow/short/SMALL. The solution is not in the hardware (especially
printers), nor in the languages, but in the display software.

My solution to this problem is to format code for an 80 line printer/terminal
(I too use an MX-80 for printing), with blank lines and comments interspersed
fairly freely. If something won't fit on the screen, I tend to bend it a
little - or better yet, try to reorganize the code. Things work great on
printers.

Then, to edit the code, I use (semi-)smart software. Editors that will let
me split the screen are a *MUST*, so I can look at a structure/define/comment
while writing the code that uses it/them. If the definition is in another file,
this feature is even more important.

Better yet are truly smart editors, that will let me elide pieces of the text.
Things like all things nested below level n, or all in-line comments, or all
comments, etc. I can chase down further references for anyone that's
interested. Or ask in net.cog-eng.

	<mike