Simon Burge <[EMAIL PROTECTED]> writes:
> I'll start looking at this. Where should I send the diffs when I'm
> done?
Are you behind a restrictive firewall where you are? If not, you can update
the files yourself using CVS (see <http://www.mhost.com/nmh/cvs.html>).
You'll need a write-access account, which you can get by emailing
Doug Morris <[EMAIL PROTECTED]>. If this isn't possible, I guess you should
mail your diffs to Doug.
> > If you do do that, perhaps you can get rid of all the snprintf() -Wall
> > warnings that appear on machines that don't have a native snprintf():
> >
> > error.c: In function `advertise':
> > error.c:92: warning: implicit declaration of function `vsnprintf'
> > error.c:106: warning: implicit declaration of function `snprintf'
> >
> > There's a million of 'em.
>
> Shouldn't be hard to do either.
Well, actually I guess I'm being a bit misleading in characterizing that as
the same problem as the local prototypes. The snprintf() guys are in a
common header which gets included by (almost?) everybody, but the prototypes
are omitted if HAVE_SNPRINTF is #defined. The thing is, that gets #defined
whether there's a native snprintf() or the nmh-included version is being
used. I guess there needs to be a different #define called NATIVE_SNPRINTF
or something...
-----------------------------------------------------------------------
Dan Harkless | To prevent SPAM contamination, please
[EMAIL PROTECTED] | do not post this private email address
SpeedGate Communications, Inc. | to the USENET or WWW. Thank you.
