BMG code, suggestions

[Seth Teller <seth@graphics.lcs.mit.edu>]

this looks a bit scary, but the code is actually
not so bad.  it's disorganized, there are a lot
of notes from the author to himself, etc.

andreas, i suggest that you analyze each file
*and subdirectory,* and classify it as:

  C source
  makefile
  perl source
  bug report
  feature request
  documentation (how to do something)
  random note
  test data
  defaults/configuration file
  etc.

and then re-organize everything into different
directories.  also, make the library and application
source siblings, rather than child and parent.  

then maybe we can get some mastery over this thing.

prof. t.