On 2018-01-04, Guido van Rossum wrote:
> We should interview you for the paper we may be writing for HOPL.
History of Programming Languages?
I did some more digging this afternoon, trying to find source code
between versions 1.0.1 and 0.9.1. No luck though. It looks like
0.9.1 might have been t
We should interview you for the paper we may be writing for HOPL.
On Wed, Jan 3, 2018 at 6:05 PM, Neil Schemenauer
wrote:
> On 2018-01-03, Guido van Rossum wrote:
> > I'm sorry, I don't think more research can convince me either way.
> > I want all three of return/break/continue to work inside f
On 2018-01-03, Guido van Rossum wrote:
> I'm sorry, I don't think more research can convince me either way.
> I want all three of return/break/continue to work inside finally
> clauses, despite there being few use cases.
That's fine. The history of 'continue' inside 'finally' is
interesting. The
I'm sorry, I don't think more research can convince me either way. I want
all three of return/break/continue to work inside finally clauses, despite
there being few use cases.
On Wed, Jan 3, 2018 at 2:30 PM, Neil Schemenauer
wrote:
> On 2018-01-03, Serhiy Storchaka wrote:
> > I haven't found 'fi
On 2018-01-03, Serhiy Storchaka wrote:
> I haven't found 'finally' clauses in
> https://github.com/gevent/gevent/blob/master/src/gevent/libev/corecffi.py.
> Perhaps this code was changed in recent versions.
Yes, I was looking at was git revision bcf4f65e. I reran my AST
checker and found this:
.
02.01.18 22:31, Neil Schemenauer пише:
Serhiy Storchaka wrote:
Currently 'break' and 'return' are never used inside 'finally'
clause in the stdlib.
See the _recv_bytes() function:
Lib/multiprocessing/connection.py: 316
Thank you Neil! I missed this case because ran only fast tests, without
Generally I think programming language implementers don't get to
decide how the language works. You just have to implement it as
specified, inconvenient as that might be.
However, from a languge design prespective, I think there is a good
argument that this is a corner of the language we should co
Serhiy Storchaka wrote:
> Currently 'break' and 'return' are never used inside 'finally'
> clause in the stdlib.
See the _recv_bytes() function:
Lib/multiprocessing/connection.py: 316
> I would want to see a third-party code that uses them.
These are the only ones I found so far:
./gevent/src
I don't think the language definition should be judgmental here. The
semantics are unambiguous.
On Dec 28, 2017 11:38 AM, "Serhiy Storchaka" wrote:
> 28.12.17 16:38, Guido van Rossum пише:
>
>> Looks to me the prohibition was to prevent a crash. It makes more sense
>> to fix it.
>>
>
> The crash
28.12.17 16:38, Guido van Rossum пише:
Looks to me the prohibition was to prevent a crash. It makes more sense
to fix it.
The crash can be fixed by just removing the check after finishing
issue17611.
But is there any use case for 'continue'/'break'/'return' inside
'finally' clause? The code
Looks to me the prohibition was to prevent a crash. It makes more sense to
fix it.
On Dec 28, 2017 03:39, "Serhiy Storchaka" wrote:
Currently 'continue' is prohibited inside 'finally' clause, but 'break' and
'return' are allowed. What is the r
'continue' was prohibited in https://bugs.python.or
11 matches
Mail list logo
