-- @(#)PROBLEMS-OTSO	5.1 --

--------------------------------------------------------------
Please add any problems/suggestions you have using OTSO here.
--------------------------------------------------------------

----------------------
General :
----------------------

- OTSO generated C++ files should have different endings (than .cxx
  and .hxx), so it would be easier to see what is produced and what isn't.

- The file /otso/system/signal.o was hacked out of /usr/lib/libc.a, by
  using the 'ar' command.  This was to prevent problems including libc.a.
  If port OTSO to a new system, and you use UNIX signals, you probably 
  have to hack signal.o out of somewhere, or add the appropriate library 
  to the loader defined in /otso/system/system.make.  The use of signals
  in OTSO is optional, see system.cxx.

----------------------
Specific :
----------------------

- The print function for OTSO Frames should be able to print ASN.1 format
  frames in a more user-friendly fashion. 

- OTSO Makefiles will probably only work with SUN make facities, should
  we convert to gnumake or imake ?

- istreams and ostreams are a problem, because of differences in the libraries
  supplied by AT&T and GNU.  for GNU's libg++, we can use ostreams and istreams,
  for AT&T's library, we have to use ofstreams and ifstreams (because the
  X::X(X&) default constructor doesn't work on AT&T istreams/ostreams.  We
  should totally replace the use of istreams/ostreams with our own class
  object, for now named a terminal, that is implemented in a compiler specific
  way.  Use of cout, cin, cerr in OTSO should be forbidden !!!, and replaced
  with a OTSO system terminal object.

- rewrite Ostream/Istream etc for ATT istreams.  too many bugs with
  Ostream << char*    char* >> Istream !
  have to always use String class instead.  really annoying.

- many compiler have problems differentiating char* and void*
  name() fn is an example in OTSO.  find out why and fix if possible
  in OTSO.
