[Python-Dev] deprecating .pyo and -O (original) (raw)
Steven D'Aprano steve at pearwood.info
Thu Jun 14 22:54:28 CEST 2012
- Previous message: [Python-Dev] deprecating .pyo and -O
- Next message: [Python-Dev] deprecating .pyo and -O
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Antoine Pitrou wrote:
Do other high-level languages have similar functionality?
Parrot (does anyone actually use Parrot?) has a byte-code optimizer.
javac -O is supposed to emit optimized byte-code, but allegedly it is a no-op.
On the other hand, the Java ecosystem includes third-party Java compilers which claim to be faster/better than Oracle's compiler, including emitting much tighter byte-code.
There are also Java byte-code optimizers such as Proguard and Soot.
By default, Perl doesn't write byte-code to files. But when it does, there are various "optimization back-ends" that you can use.
Until version 1.9, Ruby didn't even use byte-code at all.
-- Steven
- Previous message: [Python-Dev] deprecating .pyo and -O
- Next message: [Python-Dev] deprecating .pyo and -O
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]