genhatch.c:
	Hatch lines may go one pixel outside of polygon boundary. Need to use
	a smarter clipping algorithm. This isn't too bad, because on
	high-resolution output devices who cares about one pixel anyway?
	Genhatch produces a slight (one pixel) discontinuity across
	device coordinate zero (Since not many devices work with negative
	coordinates, not much of a problem. But, of course, we have one, the
	Rastertek.)
		If you go one pixel too far, then fatten the line, you have a
		very noticeable problem. -- crk

fatvec.c:
	Very fat tilted lines may leave slight gaps here and there.
	(If you don't understand what I mean, just try it.)
	Tilted lines don't fatten to the same width as vertical or horizontal
	lines.

genmarker.c:
	Use a real circle-drawing algorithm to make perfect circles,
	instead of using the ho-hum fattened Hershey-font circles.

genarea.c, polysubs.c, polyfix.c:
	Should use linked lists instead of the large static arrays it
	currently uses. Should take out the awful repeated code to do
	the preliminary clipping to each edge.
