I'm not comfortable with using log output for unit testing. You'll
discover incompatible changes in the code only at runtime, not at
compile-time. As Andreas suggests, there should be better ways even if
it means that the initial effort may be a little bigger. As an example,
look at the ElementList
On Mar 19, 2007, at 15:49, Vincent Hennebert wrote:
Does that make you feel any sudden urge to shout? ;-) Any thoughts?
Hmm, it would indeed be a bit cheap... :/
Seriously, since we're still looking for a nicer way of separating
end-user info- and error-handling and developer debug-message
Hi,
Again I'd like to share my thoughts. I've been looking for a while for
a means to unit-test the layout code. There are two difficulties
I think:
- re-creating the necessary LayoutManager structure. While it would be
great to be able to create only the necessary LMs (e.g., TableLM and
its c
