tech@mandoc.bsd.lv
 help / color / mirror / Atom feed
From: Ingo Schwarze <schwarze@usta.de>
To: Brooks Davis <brooks@freebsd.org>
Cc: tech@mandoc.bsd.lv
Subject: Re: small for FreeBSD
Date: Fri, 9 Feb 2018 01:54:00 +0100	[thread overview]
Message-ID: <20180209005400.GA36627@athene.usta.de> (raw)
In-Reply-To: <20180208234727.GA89592@spindle.one-eyed-alien.net>

Hi Brooks,

Brooks Davis wrote on Thu, Feb 08, 2018 at 11:47:27PM +0000:
> On Fri, Feb 09, 2018 at 12:40:23AM +0100, Jan Stary wrote:
> > On Feb 08 19:31:46, brooks@freebsd.org wrote:

>>> In our local tree we have this change to work around the fact that
>>> FreeBSD doesn't provide a getline() prototype unless _WITH_GETLINE is
>>> defined before stdio.h is included.  It would be nice if some variant of
>>> this could make it in to mandoc.

>> It would be way nicer if FreeBSD just provided getline(), period.

> I apologize, it looks like the need for this was removed over a year go.
> Please disregard.

You mean,

  https://svnweb.freebsd.org/base/head/include/stdio.h?r1=299574&r2=303524

?

Yeah, i think bapt@ did the right thing there.  The getline(3)
function has been in POSIX for some time now, so it makes sense
to me that FreeBSD makes it available by default, too.

Old software that defined getline() to be something else should
adapt, and i guess most was changed by now, unless it has been
totally unmaintained for a decade.

So i think we agree that no change is needed in mandoc.

Yours,
  Ingo
--
 To unsubscribe send an email to tech+unsubscribe@mandoc.bsd.lv

      reply	other threads:[~2018-02-09  0:54 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-08 19:31 Brooks Davis
2018-02-08 23:40 ` Jan Stary
2018-02-08 23:47   ` Brooks Davis
2018-02-09  0:54     ` Ingo Schwarze [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20180209005400.GA36627@athene.usta.de \
    --to=schwarze@usta.de \
    --cc=brooks@freebsd.org \
    --cc=tech@mandoc.bsd.lv \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).