Separating compat code from libfvwm

2006-07-08 Thread seventh guardian
Hi. What do you think of separating the compatibility code (replacement functions) from libfvwm? Functions like strncasecmp or strdup are spread all over the code. For systems that do not have them availiable, libfvwm is responsible for providing them. But the question is, should this be the

Re: Separating compat code from libfvwm

2006-07-08 Thread Dominik Vogt
On Sat, Jul 08, 2006 at 07:58:46PM +0100, seventh guardian wrote: Hi. What do you think of separating the compatibility code (replacement functions) from libfvwm? Functions like strncasecmp or strdup are spread all over the code. For systems that do not have them availiable, libfvwm is

Re: Separating compat code from libfvwm

2006-07-08 Thread seventh guardian
On 7/8/06, Dominik Vogt [EMAIL PROTECTED] wrote: On Sat, Jul 08, 2006 at 07:58:46PM +0100, seventh guardian wrote: Hi. What do you think of separating the compatibility code (replacement functions) from libfvwm? Functions like strncasecmp or strdup are spread all over the code. For