[vtk-developers] [EXTERNAL] Support for logging
bill.lorensen at gmail.com
Thu Aug 9 09:45:26 EDT 2018
The debug macro is only active for debug builds.
On Thu, Aug 9, 2018, 6:36 AM Allie Vacanti <allison.vacanti at kitware.com>
> While we're possibly retooling logging...
> I'd love to see the behavior of these macros change to reduce the
> verbosity. If we want vtkDebugMacro to log every set and get, ok, but it'd
> be nice to have the messages shortened. Right now, every debug/warning
> prints 3 lines, eg
> Warning: In /path/to/source/file, line XXX
> vtkClassName (0xOBJ_ADDRESS): Actual log message.
> <empty line>
> I do find the extra information to be extremely valuable, but with the
> amount of data logged by debug macros, it becomes a chore to dig through
> the output. What if the log messages were compacted to something more
> dense, like:
> [Warning] Actual log message. (vtkClassName at 0xOBJ_ADDRESS,
> Is this something that anyone else would find useful?
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the vtk-developers