Subject: Re: inet_pton() spec non-conformance
To: None <>
From: None <>
List: tech-net
Date: 02/08/2000 01:32:19
>>>If I understand the issue, you want to change inet_aton() and inet_addr().
>>>if inet_pton may not do historical processing, my suggestion is to create a
>>>new inet_pton4_internal with an additional flag parameter.
>>>if flag 0, accept historical addresses
>>>if flat 1, don't.
>>>then call inet_pton4_internal(...,...,1) from inet_pton4() and 
>>>inet_pton4_internal(...,...,0) from inet_addr and inet_aton.
>>That is the correct fix. 
>	I don't intend to change inet_{addr,aton}().  they are supposed to 
>	take short form.  the spec non-conformance is in inet_pton() only.

	For clarification: it's not short form, it's classful form. = 10.16777215
	why do we use it in cidr days :-)