Path: csiph.com!fu-berlin.de!uni-berlin.de!not-for-mail
From: Chris Angelico <rosuav@gmail.com>
Newsgroups: comp.lang.python
Subject: Re: Undefined behaviour in C [was Re: The Cost of Dynamism]
Date: Sun, 27 Mar 2016 08:58:42 +1100
Lines: 42
Message-ID: <mailman.56.1459029525.28225.python-list@python.org>
References: <mailman.8.1457732171.12893.python-list@python.org> <nc4ffn$f6s$1@dont-email.me> <56e7483d$0$1608$c3e8da3$5496439d@news.astraweb.com> <nc7kjr$jj8$1@dont-email.me> <ncnhp9$tt7$1@dont-email.me> <ncnip4$1pb$1@ger.gmane.org> <mailman.422.1458524141.12893.python-list@python.org> <ncnkma$d1i$1@dont-email.me> <mailman.425.1458526280.12893.python-list@python.org> <56ef9787$0$1516$c3e8da3$5496439d@news.astraweb.com> <mailman.433.1458546438.12893.python-list@python.org> <56f02196$0$1588$c3e8da3$5496439d@news.astraweb.com> <mailman.29.1458713374.2244.python-list@python.org> <nctrak$rbh$1@dont-email.me> <mailman.45.1458730161.2244.python-list@python.org> <ncu691$4aq$1@dont-email.me> <mailman.78.1458789868.2244.python-list@python.org> <nd0oaa$rsb$1@dont-email.me> <56f42d9f$0$1618$c3e8da3$5496439d@news.astraweb.com> <nd1ggm$v4q$1@dont-email.me> <56f55e2e$0$1619$c3e8da3$5496439d@news.astraweb.com> <ed0ba3df-5a82-48b1-bf70-90945f37e52d@googlegroups.com> <56f666d8$0$1583$c3e8da3$5496439d@news.astraweb.com> <2e1ce88d-fae2-4aa0-ace9-4faa4878459b@googlegroups.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
In-Reply-To: <2e1ce88d-fae2-4aa0-ace9-4faa4878459b@googlegroups.com>
Precedence: list
Xref: csiph.com comp.lang.python:105784

On Sun, Mar 27, 2016 at 4:43 AM, Rustom Mody <rustompmody@gmail.com> wrote:
> On Saturday, March 26, 2016 at 4:09:41 PM UTC+5:30, Steven D'Aprano wrote=
:
>> On Sat, 26 Mar 2016 04:30 pm, Rustom Mody wrote:
>>
>> > For one thing its good to remember that we wouldn't be here without py=
thon
>> > Python wouldn't be what it is without CPython
>>
>> There is nothing about Python that relies on the C standard being as it =
is.
>
> Um lets see...
> There is this nice piece of OO called the exception hierarchy:
> https://docs.python.org/2/library/exceptions.html#exception-hierarchy
>
> So we have
> BaseException =E2=8A=87 Exception =E2=8A=87 EnvironmentError =E2=8A=87 IO=
Error
> At this point it would have been completely natural for IOError to contin=
ue
> subclassing to all the typical errors
> - File not found
> - No Space left on device
> etc etc
>
> But instead we have an integer errno and we must inquire what that is to
> figure out what the exact IOError was
> Are you suggesting that python's errno module:
> https://docs.python.org/2/library/errno.html
> And C's http://man7.org/linux/man-pages/man3/errno.3.html
> are coincidentally related?

You're reading documentation that's aimed at C programmers for the
same reason as above - aiming at C makes it accessible to the most
people. But errno is not inherently bound to C; if I were to build a
language interpreter in Fortran, I could make errno available to it.
What you're looking at isn't so much a C thing as a Linux thing;
Python makes available the Linux error code as a means of
disambiguating similar errors.

ChrisA