On Wed, Jul 05, 2006 at 02:35:10PM +0100, seventh guardian wrote:
On 7/5/06, seventh guardian [EMAIL PROTECTED] wrote:
Hi.
I have found FVWM_DEBUG_MSGS and DEBUG ifdef's all over the code (as
expected). But it seems to me they are allways used at the same time,
one defining the other, and
On 7/6/06, Dominik Vogt [EMAIL PROTECTED] wrote:
On Wed, Jul 05, 2006 at 02:35:10PM +0100, seventh guardian wrote:
On 7/5/06, seventh guardian [EMAIL PROTECTED] wrote:
Hi.
I have found FVWM_DEBUG_MSGS and DEBUG ifdef's all over the code (as
expected). But it seems to me they are allways
On Thu, Jul 06, 2006 at 04:22:28PM +0100, seventh guardian wrote:
On 7/6/06, Dominik Vogt [EMAIL PROTECTED] wrote:
On Wed, Jul 05, 2006 at 02:35:10PM +0100, seventh guardian wrote:
On 7/5/06, seventh guardian [EMAIL PROTECTED] wrote:
Hi.
I have found FVWM_DEBUG_MSGS and DEBUG ifdef's
Hi.
I have found FVWM_DEBUG_MSGS and DEBUG ifdef's all over the code (as
expected). But it seems to me they are allways used at the same time,
one defining the other, and thus replaceable just by one of them. Is
this true or do they have distinct purposes?
This supports my theory (from
On 7/5/06, seventh guardian [EMAIL PROTECTED] wrote:
Hi.
I have found FVWM_DEBUG_MSGS and DEBUG ifdef's all over the code (as
expected). But it seems to me they are allways used at the same time,
one defining the other, and thus replaceable just by one of them. Is
this true or do they have
