140316

I got set_filt.exe working.  BUFFSIZE is 8000.  I increased it from 2000.
I haven't tried 4000.  Hmmm.

I could put the case statement into a "if (!dump)" block instead of just
checking dump before printing.  That might speed things up.  I tried ending
the reading from standard input on dump, but that breaks the pipe and there
is a complaint.

160409

I need to comment on this dir.  I forgot what it was for.  I used diff
to compare source and source2, and it seem pretty clear that I made
this dir to work on an alternate set_filt.c.  I would guess that
nothing in this dir is currently in use.

But I would be wrong.  I did

   diff set_filt.exe source2/set_filt.exe

when in the dir above this one.  It showed that set_filt.exe from this
dir is in use.  Not conclusive.  I would have to compile again to be
sure.

I looked at my notes about what I did in the source code.  It seems
that I had good intentions to make improvements regarding the handling
of unpaired single quotes.  It seems I had intended to change the code
so that an unpaired single quote wouldn't cause an error if it was
escaped with "\".

Just today (and at least once in the previous years) I accidentally fed
set_filt.exe an unpaired single quote that wasn't escaped.  I got an
error message from set_filt.exe.  The unpaired single quote was an
apostrophe in the word "don't".  The word appeared in an echo statement
in a function that I wrote.  Bash has no trouble with an unpaired
single quote between a pair of double quotes, and it seems the vice
versa is true also.  So it seems I should fix set_filt.c again to
behave this way.

In the meantime I solved the problem by escaping the apostrophe. 
However to do this I had to remove the double quotes in which I had
enclosed the whole string that was being echoed.  Otherwise, although
the "\" worked to stop the error, it was printed by the echo command. 
Ha.

160409

I'm working on fixing set_filt.c to use both instring and indouble
variables.
