Syslog.h
Tony van der Hoff
tony at mk-net.demon.co.uk
Tue May 4 17:52:13 BST 2004
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. (x)syslog_close_session_log wants a char* when the docs say it
> requires an (unsigned ?) int and (x)syslog_open_session_log returns a
> char* when the docs say it returns an (unsigned ?) int.
>
OK, those changes are in CVS. Are you desperate for a new build? The last
one was 6.60 at end Dec; I don't think it's a good idea to release at more
than 6-monthly intervals, but am happy to do so if peeps want it...
Cheers,
Tony
--
Tony van der Hoff
Buckinghamshire England
More information about the oslib-user
mailing list