[Gnucap-devel] io_trace

[Felix Salfelder]

hi Al

now theres gnucap-conf. starting to build things...

i have become used to a slightly different trace header (in -uf). not
all changes make sense, but i think these (see traces branch on sv).

- catch stale traces. by defining trace* to ignore the arguments, a lot
  of cruft will accumulate and make it harder to switch them back on.
  also, unused variable warnings show up for variables that are used for
  traces. my "solution" is to define inactive traces as

  #define trace(x) (1)?(void)(0):(void)(x),

  instead of nothing. this way, the compiler checks x, without actually
  doing anything. maybe there is a simpler way, this one does not look
  dangerous...

- use ostreams instead of printf. i have used this to debug non-numeric
  objects, or matrices/vectors. this seems fully backwars compatible and
  harmless to me. but useful.

thanks
felix