RetroSearch Browse

Thu Sep 17 18:41:18 CEST 2009 · http://mail.python.org/pipermail/python-dev/2009-September/091832.html

On Thu, Sep 17, 2009 at 9:26 AM, Antoine Pitrou <solipsis at pitrou.net> wrote:
> Peter Moody <peter <at> hda3.com> writes:
>>
>> Again, the same error-catching functionality can be obtained through
>> an option to the constructor. network and broadcast attributes can be
>> renamed to .\1_address to alleviate confusion as well.
>
> My remark was not targetting error-catching of non-zero low bits, it was about
> the suggestion to have a "network" or "mask" attribute on Address objects.

If I'm reading your reply correctly, then I agree that having a
network attribute on an address object doesn't make sense.

My remark was targeting Eric's reply of, "By keeping the concepts
distinct we can catch mis-uses earlier."

Cheers,
/peter

> Regards
>
> Antoine.
>
>
> _______________________________________________
> Python-Dev mailing list
> Python-Dev at python.org
> http://mail.python.org/mailman/listinfo/python-dev
> Unsubscribe: http://mail.python.org/mailman/options/python-dev/python-dev%40hda3.com
>

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from http://mail.python.org/pipermail/python-dev/2009-September/091832.html below:

[Python-Dev] conceptual clarity