Syslog.h
Philip Ludlam
philip at philipnet.com
Tue May 4 19:48:56 BST 2004
On 4 May, in message <gemini.hx78710eun98g01rp.tony at mk-net.demon.co.uk>
Tony van der Hoff <tony at mk-net.demon.co.uk> wrote:
>Philip Ludlam <philip at philipnet.com> wrote in message
><07cfd6a84c.philip at philipnet.com>
>
>> On 2 May, in message <gemini.hx34xt04f3nzk01rp.tony at mk-net.demon.co.uk>
>> Tony van der Hoff <tony at mk-net.demon.co.uk> wrote:
>>
>> >Philip Ludlam <philip at philipnet.com> wrote in message
>> ><a15235a84c.philip at philipnet.com>
>> >
>> >> Dear All,
>[snip]
>>
>> > As for a fix, I think maybe the best way to do this is to define a
>> > second set of functions, so that we get something like:
>> >
>> > syslog_log_message( char const *name, char const *message, int priority
>> > );
>> >
>> > and
>> >
>> > syslog_log_message_handle( int handle, char const *message, int priority
>> > );
>> >
>> > The former is backward-compatible.
>> >
>> > I would also favour deprecating the syslog_open_session_log() and
>> > syslog_close_session_log() calls, which don't make a lot of sense in
>> > favour of new syslog_open_session_log_handle() and
>> > syslog_close_session_log_handle() calls.
>>
>> Quite.
[snip]
>OK, those changes are in CVS. Are you desperate for a new build?
Not particularly. Release it when you want (preferably after I get my
hands on a copy of ObjAsm that handles the -I argument properly :-) ).
Yours,
Phil L.
--
http://www.philipnet.com | http://director.sourceforge.net
More information about the oslib-user
mailing list