← Back to team overview

yade-dev team mailing list archive

log4cxx, logging

 

Vaclav,

Also I think that log4cxx is not used. Even you are not using it, as
you prefer std::cerr than fiddling with log4cxx config files for one
stupid std::cerr output. I've seen it only once, when you were doing
something with yade and I was looking - I got the impression that
fiddling with this config was too troublesome for you. In fact I
don't even know which config file, and how to change it. So I can't
use log4cxx

I want to replace log4cxx with a dedicated class, which is also
declared in int main () {}. Like YadeLog (or similar name).
And now we will write sth. like:

  log << "...";
or
  log(severity,string);

And the frontend will handle this properly: GUI will print it in nice
window, CLI will use std::cerr, etc...


YadeSimulation,YadeLog and other toplevel classes will be passed as
an argument from the top using "Encapsulated Context" C++ pattern.
You can read about this on the web:

http://www.allankelly.net/patterns/encapsulatecontext.pdf

-- 
Janek Kozicki                                                         |
_______________________________________________
yade-dev mailing list
yade-dev@xxxxxxxxxxxxxxxx
https://lists.berlios.de/mailman/listinfo/yade-dev



Follow ups