Return Styles: Pseud0ch, Terminal, Valhalla, NES, Geocities, Blue Moon.

Pages: 1-

Python is a Nonsense

Name: Anonymous 2016-10-21 15:42

Name: Anonymous 2016-10-21 16:24

Jesus, Python is terrible, people should jump to Perl 6 now that is available.

Name: Anonymous 2016-10-21 16:50

Wait a minute: it resolves global symbol names at fucking runtime?!?

Name: Anonymous 2016-10-21 17:12

>>3
welcome to interpreter

Name: Anonymous 2016-10-21 20:22

>>4
But they mention local vars being stored in some kind of array, and the code being 'compiled to bytecode' (read: binary) before being run?!?

Name: Anonymous 2016-10-21 20:33

Python is so fucking terrible, I just laugh when people try to compare it to Ruby or Perl.

Name: Anonymous 2016-10-21 20:40

>>5
The interpret the bytecode. It is binary yes, but it is not machine code for a conventional machine, but an idealized machine.

There are various types of interpreters. The simplest are syntax directed interpreters. They execute code, when the parser recognizes a piece of syntax. These are relatively slow, I think PHP is such a language.

Then you have the tree walkers. They parse the code into a proper AST. Perhaps optimize it a bit and then walk the AST, while executing code.

Python is a bit more sophisticated. The AST is here translated into bytecode, instructions of an idealized machine.

Java also runs on an idealized machine, but is much more sophisticated.

Name: Anonymous 2016-10-21 20:47

>>5

The interesting thing about bytecode is, that you could design a CPU running it. E.g. ARM processors have a specialized instruction set for running JVM instructions. Also various language specific CPU's have been designed. The most interesting one I find is GA144 from green arrays: http://www.greenarraychips.com/

It runs a dialect of Forth natively. It's cores are asynchronous. This has some advantages. If a core is idle, it really doesn't do anything. Good for getting the power consumption down.

Name: Anonymous 2016-10-21 21:10

python is a codeword for anti white

Name: Anonymous 2016-10-22 15:22

>>4
That has nothing to do with code being interpreted. It can still resolve global variables at startup time. The problem is more related to Python's broken language design and dynamic scoping, where global variables can be introduced at runtime for no good reason. Although even in that case, there can be special case for already known variables, so only unknown ones will go into hash table, like in Common Lisp.

Name: Anonymous 2016-10-22 15:50

Dubs

Don't change these.
Name: Email:
Entire Thread Thread List