[last updated 01/12/94]
Strn code styles and (mis?)features.

	I highly recommend reading the HACKERSGUIDE in the TRN
distribution.  While I haven't followed all the guidelines, they are
well worth reading.


	Early strn testing occurred on Decstation 5000s of varying
capacities running ULTRIX, connected to an NNTP server running INN 1.2
with the XTHREAD extensions.  Currently (01/12/94) strn work is done
on a Sun running Sunos 4.1.3, connected to an INN 1.4 server.

	The strn code was initially intended as a prototype

Code style:
* I like lots of small functions and long descriptive names.

* When in doubt, I comment.

* I don't really like global variables, but I prefer them to passing
  zillions of arguments.

Deficiencies:
* I overuse local buffers.  This is *bad*, although it saves a lot of time.

* My most common mistake is copying a similar segment of code and not
fully changing the copy to its new functionality.

* Ints, longs, and ART_NUMS are mixed fairly freely, and I have very little
  hope of changing that soon.

* The entry numbers really should have their own typedef.  (In the
  meantime, use longs instead of ints.)

* Gotos are used, sometimes a little too freely.

...Much of the "sloppy code" in strn should be replaced in the next
major rewrite.  This rewrite will not occur soon.

The "Nice Background" feature:

	* The NICEBG code in term.c seems to work now, but it
might need a bit of work.  If you have problems with keyboard input,
try defining the debugging #define just before wait_key_pause.  The
NBG_SELECT method is used by default--if this doesn't work please let
me (caadams@access.digex.net) know and I'll suggest something else.

	* The "nice background" feature depends on a working select() call.
	  (I've learned not to assume that operating systems will get
	   the basics right.)
