From mboxrd@z Thu Jan 1 00:00:00 1970 MIME-Version: 1.0 In-Reply-To: References: Date: Sun, 9 Sep 2012 04:01:36 +0100 Message-ID: From: Charles Forsyth To: cinap_lenrek@gmx.de Content-Type: multipart/alternative; boundary=047d7b33daf42592c004c93c0f03 Cc: 9fans@9fans.net Subject: Re: [9fans] dns Topicbox-Message-UUID: b7a8151e-ead7-11e9-9d60-3106f5b1d025 --047d7b33daf42592c004c93c0f03 Content-Type: text/plain; charset=UTF-8 No, I didn't explain it well. NETPATHLEN isn't named in the manual pages, so ndb/dns doesn't use it. On the other hand, dial does, but because it's ...LEN, it's an easy mistake to think of it as the length of a string, which wouldn't include the terminating zero byte, instead of the length of the underlying array. On 9 September 2012 03:37, wrote: > ah, so NETPATHLEN was introduced later and is really refering to > the number of non null characters? and there was never an official > named constant for the size of the netdir buffers for dial/annouce? > thats indeed confusing. > > -- > cinap > --047d7b33daf42592c004c93c0f03 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable No, I didn't explain it well.
NETPATHLEN isn't named in the man= ual pages, so ndb/dns doesn't use it.
On the other hand, dial= does, but because it's ...LEN, it's an easy mistake
to t= hink of it as the length of =C2=A0a string, which wouldn't include the = terminating zero byte,
instead of the length of the underlying array.

On 9 September 2012 03:37, <cinap_lenrek@gmx.de> wrote:
ah, so NETPATHLEN was introduced later and i= s really refering to
the number of non null characters? and there was never an official
named constant for the size of the netdir buffers for dial/annouce?
thats indeed confusing.

--
cinap

--047d7b33daf42592c004c93c0f03--