http://bugzilla.moblin.org/show_bug.cgi?id=5041
--- Comment #4 from yongsheng zhu <[email protected]> 2010-03-16 19:30:11 PST --- (In reply to comment #0) > Usage of stdout and cout should be avoided. Currently the SyncEvolutionCmdline > class is still told to write into cout by syncevolution.cpp. > > When compiling SyncEvolution .cpp code, any reference to stdout or cout should > trigger a compiler error (redefine the symbols?!). Some with printf, puts, > etc. you mean all files in SyncEvolution core or just syncevolution.cpp? If yes, > Instead of cout, a custom stream which passes the data into our logging system > with a suitable tag that reproduces the output verbatim on the console and > logs > it in the normal log should be used. it's good for command line. what's the 'tag' for? to determine whether to reproduce the output on the console or log it in the normal log, or both? Since dbus server might also call Cmdline class, I think the custom stream for it might be changed: log it to normal system and send them to dbus client. > Running commands must redirect stdout of the processes and ideally keep > processing that output while the command runs (rules out simple system() > calls). I don't understand it. Redirect stdout of processes which are started by syncevolution? -- Configure bugmail: http://bugzilla.moblin.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching the assignee of the bug. You are watching someone on the CC list of the bug. _______________________________________________ Syncevolution-issues mailing list [email protected] http://lists.syncevolution.org/listinfo/syncevolution-issues
