Re: Evolution of python

You can do vast disruption to the semantic meaning of a Python program by removing even a single 0x09 ASCII byte from the source code ... anywhere. Unlike braces, there is nothing to counter-balance the perhaps purely accidental removal of a TAB: there is no (missing ...) '}' which would allow the compiler to catch your mistake.

Comment on Re: Evolution of python

Replies are listed 'Best First'.
Re^2: Evolution of python by QM (Parson) on Jul 10, 2019 at 11:04 UTC
The "significant whitespace problem" is one of the drawbacks of Python, IMO. I thought we deprecated that way back in `make`? That is, why would someone choose to do that, after having suffered through using `make`? In Python, I also miss having an enclosing block entity, to limit the scope of variables. And it seems it's too easy to accidentally create a tuple by grouping things in parens, which then returns the wrong type to something not expect an iterable. ARG! -QM -- Quantum Mechanics: The dreams stuff is made of	[reply] [d/l] [select]

Replies are listed 'Best First'.

Re^2: Evolution of python
by QM (Parson) on Jul 10, 2019 at 11:04 UTC

make

In Python, I also miss having an enclosing block entity, to limit the scope of variables.

And it seems it's too easy to accidentally create a tuple by grouping things in parens, which then returns the wrong type to something not expect an iterable. ARG!

-QM
--
Quantum Mechanics: The dreams stuff is made of

[reply]
[d/l]
[select]