List Info

Thread: conflict between YAZ and syslog.h




conflict between YAZ and syslog.h
user name
2006-11-09 15:39:00
Hello,
as widely known, there is a naming conflict for LOG_DEBUG
between YAZ
(log.h) and syslog.h

This can be solved by using:

#define YAZ_USE_NEW_LOG 1

before including YAZ stuff in my backend.

simple question: is this always safe to do?

Ko vd Sloot

_______________________________________________
Yazlist mailing list
Yazlistlists.indexdata.dk
http://lists.indexdata.dk/cgi-bin/mailman/listinfo/yaz
list
conflict between YAZ and syslog.h
user name
2006-11-10 09:36:41
Ko van der Sloot wrote:
> Hello,
> as widely known, there is a naming conflict for
LOG_DEBUG between YAZ
> (log.h) and syslog.h
> 
> This can be solved by using:
> 
> #define YAZ_USE_NEW_LOG 1
> 
> before including YAZ stuff in my backend.
> 
> simple question: is this always safe to do?
Quite safe. And much nicer than having to deal with name
conflicts.

But this could be the time where we go reverse! Just do the
right thing 
and omit the old defines unless a #define YAZ_USE_OLD_LOG=1
?

This would not break binary compatibility. But old
applications would 
have to patched to use the new log defines or just set
YAZ_USE_OLD_LOG.

/ Adam

> 
> Ko vd Sloot
> 
> _______________________________________________
> Yazlist mailing list
> Yazlistlists.indexdata.dk
> http://lists.indexdata.dk/cgi-bin/mailman/listinfo/yaz
list
> 
> .
> 


_______________________________________________
Yazlist mailing list
Yazlistlists.indexdata.dk
http://lists.indexdata.dk/cgi-bin/mailman/listinfo/yaz
list
conflict between YAZ and syslog.h
user name
2006-11-10 09:52:05
Adam Dickmeiss wrote:
> Ko van der Sloot wrote:
>> Hello,
>> as widely known, there is a naming conflict for
LOG_DEBUG between YAZ
>> (log.h) and syslog.h
>>
>> This can be solved by using:
>>
>> #define YAZ_USE_NEW_LOG 1
>>
>> before including YAZ stuff in my backend.
>>
>> simple question: is this always safe to do?
> Quite safe. And much nicer than having to deal with
name conflicts.
> 
> But this could be the time where we go reverse! Just do
the right thing
> and omit the old defines unless a #define
YAZ_USE_OLD_LOG=1
> ?

Go ahead!

> This would not break binary compatibility. But old
applications would
> have to patched to use the new log defines or just set
YAZ_USE_OLD_LOG.

No problem for me, but it might be a problem for some people
to rebuild
old apps.
maybe introduce yaz3 ?

> / Adam
> 
>>
>> Ko vd Sloot

Ko vd Sloot

_______________________________________________
Yazlist mailing list
Yazlistlists.indexdata.dk
http://lists.indexdata.dk/cgi-bin/mailman/listinfo/yaz
list
[1-3]

about | contact  Other archives ( Real Estate discussion Medical topics )