From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jeff Sickel Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <17666A31-B506-46C1-972F-2D6407C4B8DD@corpus-callosum.com> Date: Fri, 29 Mar 2013 12:13:23 -0500 To: "9fans@9fans.net Bell Labs" <9fans@9fans.net> Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\)) Subject: [9fans] APE inconsistencies Topicbox-Message-UUID: 39d35832-ead8-11e9-9d60-3106f5b1d025 Does anyone know if the netdb.h inclusion of hstrerror(int) was just a copy/paste error? Of if hstrerror() was intended to be in the ape/lib/bsd source but got dropped somehow? -jas From mboxrd@z Thu Jan 1 00:00:00 1970 MIME-Version: 1.0 In-Reply-To: <17666A31-B506-46C1-972F-2D6407C4B8DD@corpus-callosum.com> References: <17666A31-B506-46C1-972F-2D6407C4B8DD@corpus-callosum.com> Date: Fri, 29 Mar 2013 17:20:05 +0000 Message-ID: From: Charles Forsyth To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> Content-Type: multipart/alternative; boundary=047d7bf1984472ab3e04d9137b78 Subject: Re: [9fans] APE inconsistencies Topicbox-Message-UUID: 39d92eec-ead8-11e9-9d60-3106f5b1d025 --047d7bf1984472ab3e04d9137b78 Content-Type: text/plain; charset=UTF-8 On 29 March 2013 17:13, Jeff Sickel wrote: > Does anyone know if the netdb.h inclusion of hstrerror(int) was > just a copy/paste error? Of if hstrerror() was intended to be > in the ape/lib/bsd source but got dropped somehow? > the linux manual page describes hstrerror as obsolete --047d7bf1984472ab3e04d9137b78 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

= On 29 March 2013 17:13, Jeff Sickel <jas@corpus-callosum.com>= wrote:
Does anyone know if the net= db.h inclusion of hstrerror(int) was
just a copy/paste error? =C2=A0Of if hstrerror() was intended to be
in the ape/lib/bsd source but got dropped somehow?
=
the linux manual page describes hstrerror as obsolete
--047d7bf1984472ab3e04d9137b78-- From mboxrd@z Thu Jan 1 00:00:00 1970 Content-Type: text/plain; charset=windows-1252 Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\)) From: Jeff Sickel In-Reply-To: Date: Fri, 29 Mar 2013 12:25:04 -0500 Content-Transfer-Encoding: quoted-printable Message-Id: References: <17666A31-B506-46C1-972F-2D6407C4B8DD@corpus-callosum.com> To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> Subject: Re: [9fans] APE inconsistencies Topicbox-Message-UUID: 39e0230a-ead8-11e9-9d60-3106f5b1d025 On Mar 29, 2013, at 12:20 PM, Charles Forsyth = wrote: > the linux manual page describes hstrerror as obsolete Which distro? So many to choose from=85 From mboxrd@z Thu Jan 1 00:00:00 1970 Date: Fri, 29 Mar 2013 13:41:48 -0400 From: Kurt H Maier To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> Message-ID: <20130329174148.GA98286@intma.in> References: <17666A31-B506-46C1-972F-2D6407C4B8DD@corpus-callosum.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: Content-Transfer-Encoding: quoted-printable Subject: Re: [9fans] APE inconsistencies Topicbox-Message-UUID: 39eb7af2-ead8-11e9-9d60-3106f5b1d025 On Fri, Mar 29, 2013 at 12:25:04PM -0500, Jeff Sickel wrote: >=20 > On Mar 29, 2013, at 12:20 PM, Charles Forsyth wrote: >=20 > > the linux manual page describes hstrerror as obsolete >=20 > Which distro? So many to choose from=E2=80=A6 >=20 It's sort of moot, since The Man wants you to stop using gethostbyname and friends anyway. They're marked as 'obsolete' because POSIX.1-2001 wants you to use getnameinfo et al. instead. Anything using gethostbyname is probably going to want herror (and thus hstrerror) to be there. khm From mboxrd@z Thu Jan 1 00:00:00 1970 MIME-Version: 1.0 In-Reply-To: <20130329174148.GA98286@intma.in> References: <17666A31-B506-46C1-972F-2D6407C4B8DD@corpus-callosum.com> <20130329174148.GA98286@intma.in> Date: Fri, 29 Mar 2013 18:00:45 +0000 Message-ID: From: Charles Forsyth To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> Content-Type: multipart/alternative; boundary=f46d04462e7ae5852904d9140c62 Subject: Re: [9fans] APE inconsistencies Topicbox-Message-UUID: 39f1c48e-ead8-11e9-9d60-3106f5b1d025 --f46d04462e7ae5852904d9140c62 Content-Type: text/plain; charset=UTF-8 On 29 March 2013 17:41, Kurt H Maier wrote: > Anything using gethostbyname is probably going to want herror (and thus > hstrerror) to be there. > I see, although it seems herror/hstrerror is usually ifdef'd out, even when gethostbyname remains! --f46d04462e7ae5852904d9140c62 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

= On 29 March 2013 17:41, Kurt H Maier <khm-9@intma.in> wrote:
Anything using gethostbyname is probably going to want her= ror (and thus
hstrerror) to be there.

I see, although it seem= s herror/hstrerror is usually ifdef'd out, even when gethostbyname rema= ins!
--f46d04462e7ae5852904d9140c62-- From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jeff Sickel Content-Type: multipart/alternative; boundary="Apple-Mail=_875B50E8-E198-401F-81F8-6C9CF95D1678" Message-Id: <24472F85-7A42-4CDD-8CF2-5A1CEB25E109@corpus-callosum.com> Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\)) Date: Fri, 29 Mar 2013 13:26:53 -0500 References: <17666A31-B506-46C1-972F-2D6407C4B8DD@corpus-callosum.com> <20130329174148.GA98286@intma.in> To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> In-Reply-To: Subject: Re: [9fans] APE inconsistencies Topicbox-Message-UUID: 39f78414-ead8-11e9-9d60-3106f5b1d025 --Apple-Mail=_875B50E8-E198-401F-81F8-6C9CF95D1678 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii On Mar 29, 2013, at 1:00 PM, Charles Forsyth = wrote: >=20 > On 29 March 2013 17:41, Kurt H Maier wrote: > Anything using gethostbyname is probably going to want herror (and = thus > hstrerror) to be there. >=20 > I see, although it seems herror/hstrerror is usually ifdef'd out, even = when gethostbyname remains! Though if I check recent FreeBSD manuals, it's all there. And given = that this is part of the BSD extensions to APE, those might be more relevant than the Linux man pages. Not that BSD tries to be POSIX compliant any more or less than GNU/Linux. There are definitely some issues in gethostbyaddr() that are being looked into at this time. But while the review is taking place, it = doesn't hurt to look at other potential areas of a mismatch. --Apple-Mail=_875B50E8-E198-401F-81F8-6C9CF95D1678 Content-Transfer-Encoding: 7bit Content-Type: text/html; charset=us-ascii
On Mar 29, 2013, at 1:00 PM, Charles Forsyth <charles.forsyth@gmail.com> wrote:


On 29 March 2013 17:41, Kurt H Maier <khm-9@intma.in> wrote:
Anything using gethostbyname is probably going to want herror (and thus
hstrerror) to be there.

I see, although it seems herror/hstrerror is usually ifdef'd out, even when gethostbyname remains!


Though if I check recent FreeBSD manuals, it's all there.  And given that
this is part of the BSD extensions to APE, those might be more relevant
than the Linux man pages.  Not that BSD tries to be POSIX compliant
any more or less than GNU/Linux.

There are definitely some issues in gethostbyaddr() that are being
looked into at this time.  But while the review is taking place, it doesn't
hurt to look at other potential areas of a mismatch.

--Apple-Mail=_875B50E8-E198-401F-81F8-6C9CF95D1678-- From mboxrd@z Thu Jan 1 00:00:00 1970 Date: Fri, 29 Mar 2013 20:03:45 +0100 From: tlaronde@polynum.com To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> Message-ID: <20130329190345.GA2335@polynum.com> References: <17666A31-B506-46C1-972F-2D6407C4B8DD@corpus-callosum.com> <20130329174148.GA98286@intma.in> <24472F85-7A42-4CDD-8CF2-5A1CEB25E109@corpus-callosum.com> Mime-Version: 1.0 In-Reply-To: <24472F85-7A42-4CDD-8CF2-5A1CEB25E109@corpus-callosum.com> User-Agent: Mutt/1.4.2.3i Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Subject: Re: [9fans] APE inconsistencies Topicbox-Message-UUID: 39fecabc-ead8-11e9-9d60-3106f5b1d025 On Fri, Mar 29, 2013 at 01:26:53PM -0500, Jeff Sickel wrote: > > Though if I check recent FreeBSD manuals, it's all there. And given that > this is part of the BSD extensions to APE, those might be more relevant > than the Linux man pages. Not that BSD tries to be POSIX compliant > any more or less than GNU/Linux. > It should be indeed underlined that this is a compatibility feature, and not a POSIX feature. It seems that it is still here for legacy compatibility on BSD (it is still here in NetBSD for example) but the question arises whether it is worth supporting (because starting to support all not POSIX is a daunting task). This is what is said in the APE paper. The problem is not with Plan9 APE, it is that there are not a lot of programs that are written in a POSIX compliant way... -- Thierry Laronde http://www.kergis.com/ Key fingerprint = 0FF7 E906 FBAF FE95 FD89 250D 52B1 AE95 6006 F40C From mboxrd@z Thu Jan 1 00:00:00 1970 Date: Fri, 29 Mar 2013 15:12:20 -0400 From: Kurt H Maier To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> Message-ID: <20130329191220.GA9082@intma.in> References: <17666A31-B506-46C1-972F-2D6407C4B8DD@corpus-callosum.com> <20130329174148.GA98286@intma.in> <24472F85-7A42-4CDD-8CF2-5A1CEB25E109@corpus-callosum.com> <20130329190345.GA2335@polynum.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20130329190345.GA2335@polynum.com> Subject: Re: [9fans] APE inconsistencies Topicbox-Message-UUID: 3a123ea8-ead8-11e9-9d60-3106f5b1d025 On Fri, Mar 29, 2013 at 08:03:45PM +0100, tlaronde@polynum.com wrote: > On Fri, Mar 29, 2013 at 01:26:53PM -0500, Jeff Sickel wrote: > > > > Though if I check recent FreeBSD manuals, it's all there. And given that > > this is part of the BSD extensions to APE, those might be more relevant > > than the Linux man pages. Not that BSD tries to be POSIX compliant > > any more or less than GNU/Linux. > > > > It should be indeed underlined that this is a compatibility feature, and > not a POSIX feature. It seems that it is still here for legacy > compatibility on BSD (it is still here in NetBSD for example) but the > question arises whether it is worth supporting (because starting to > support all not POSIX is a daunting task). > > This is what is said in the APE paper. The problem is not with Plan9 > APE, it is that there are not a lot of programs that are written in a > POSIX compliant way... > It is a POSIX feature, I think. It's just an outmoded one. Supporting all revisions of POSIX is damn near impossible. Does APE have an explicit target? khm From mboxrd@z Thu Jan 1 00:00:00 1970 Date: Fri, 29 Mar 2013 21:10:35 +0100 From: tlaronde@polynum.com To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> Message-ID: <20130329201035.GA3950@polynum.com> References: <17666A31-B506-46C1-972F-2D6407C4B8DD@corpus-callosum.com> <20130329174148.GA98286@intma.in> <24472F85-7A42-4CDD-8CF2-5A1CEB25E109@corpus-callosum.com> <20130329190345.GA2335@polynum.com> <20130329191220.GA9082@intma.in> Mime-Version: 1.0 In-Reply-To: <20130329191220.GA9082@intma.in> User-Agent: Mutt/1.4.2.3i Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Subject: Re: [9fans] APE inconsistencies Topicbox-Message-UUID: 3a1b35f8-ead8-11e9-9d60-3106f5b1d025 On Fri, Mar 29, 2013 at 03:12:20PM -0400, Kurt H Maier wrote: > > It is a POSIX feature, I think. It's just an outmoded one. Supporting > all revisions of POSIX is damn near impossible. Does APE have an > explicit target? Well, it is not in SuSv3. And this is not already the latest... -- Thierry Laronde http://www.kergis.com/ Key fingerprint = 0FF7 E906 FBAF FE95 FD89 250D 52B1 AE95 6006 F40C From mboxrd@z Thu Jan 1 00:00:00 1970 MIME-Version: 1.0 In-Reply-To: <20130329201035.GA3950@polynum.com> References: <17666A31-B506-46C1-972F-2D6407C4B8DD@corpus-callosum.com> <20130329174148.GA98286@intma.in> <24472F85-7A42-4CDD-8CF2-5A1CEB25E109@corpus-callosum.com> <20130329190345.GA2335@polynum.com> <20130329191220.GA9082@intma.in> <20130329201035.GA3950@polynum.com> Date: Fri, 29 Mar 2013 20:32:45 +0000 Message-ID: From: Charles Forsyth To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> Content-Type: multipart/alternative; boundary=f46d0438ee617bbe8104d9162c8e Subject: Re: [9fans] APE inconsistencies Topicbox-Message-UUID: 3a219ac4-ead8-11e9-9d60-3106f5b1d025 --f46d0438ee617bbe8104d9162c8e Content-Type: text/plain; charset=UTF-8 On 29 March 2013 20:10, wrote: > > It is a POSIX feature, I think. It's just an outmoded one. Supporting > > all revisions of POSIX is damn near impossible. Does APE have an > > explicit target? > I think it's really a pragmatic matter of which interfaces are in some standard that can be named, that are also needed by most software that's being imported (eg, newer versions of Python). --f46d0438ee617bbe8104d9162c8e Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

= On 29 March 2013 20:10, <tlaronde@polynum.com> wrote:
> It is a POSIX feature, I think. =C2=A0It's just = an outmoded one. =C2=A0Supporting
> all revisions of POSIX is damn near impossible. =C2=A0Does APE have an=
> explicit target?

I think it's real= ly a pragmatic matter of which interfaces are in some standard that can be = named,
that are also needed by most s= oftware that's being imported (eg, newer versions of Python).
--f46d0438ee617bbe8104d9162c8e-- From mboxrd@z Thu Jan 1 00:00:00 1970 References: <17666A31-B506-46C1-972F-2D6407C4B8DD@corpus-callosum.com> <20130329174148.GA98286@intma.in> <24472F85-7A42-4CDD-8CF2-5A1CEB25E109@corpus-callosum.com> In-Reply-To: <24472F85-7A42-4CDD-8CF2-5A1CEB25E109@corpus-callosum.com> Mime-Version: 1.0 (Apple Message framework v1085) Content-Type: text/plain; charset=us-ascii Message-Id: <4F539D6A-0B72-4D02-9266-C962735F2467@orthanc.ca> Content-Transfer-Encoding: quoted-printable From: Lyndon Nerenberg Date: Fri, 29 Mar 2013 15:20:01 -0700 To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> Subject: Re: [9fans] APE inconsistencies Topicbox-Message-UUID: 3a4a7318-ead8-11e9-9d60-3106f5b1d025 On 2013-03-29, at 11:26 AM, Jeff Sickel wrote: > Not that BSD tries to be POSIX compliant > any more or less than GNU/Linux. FreeBSD is actually pretty good about adhering to POSIX/SUS/Xopen when = you set the appropriate defines. From mboxrd@z Thu Jan 1 00:00:00 1970 To: 9fans@9fans.net Date: Fri, 29 Mar 2013 22:37:59 -0400 From: a@9srv.net Message-ID: <299894e4d6e9869eeb1b646ac9dd22bb@9srv.net> In-Reply-To: <20130329190345.GA2335@polynum.com> References: <17666A31-B506-46C1-972F-2D6407C4B8DD@corpus-callosum.com> <20130329174148.GA98286@intma.in> <24472F85-7A42-4CDD-8CF2-5A1CEB25E109@corpus-callosum.com> <20130329190345.GA2335@polynum.com> MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit Subject: Re: [9fans] APE inconsistencies Topicbox-Message-UUID: 3abf8892-ead8-11e9-9d60-3106f5b1d025 > It should be indeed underlined that this is a compatibility > feature, and not a POSIX feature. APE does an excellent job of making that distinction clear. Its use of defines to forcibly break syntax was quite educational as a young programmer. Anthony