News for hackers. Stuff that matters.
Re:Why I wrote a book about interpreters by bretthoerner on Thursday December 01, 2016 @06:40PM (#13084668)
> Python is not usually considered a compiler, even though it writes .pyc files to disk, because its output is bytecode that only Python itself is expected to understand.

I'd disagree, simply because this is exactly what javac does too.

Re:Why I wrote a book about interpreters by haberman on Friday December 02, 2016 @10:40AM (#13089452)
Java bytecode is standardized. So any JVM implementing the spec should be able to interpret the output of javac:

http://docs.oracle.com/javase/specs/jvms/se7/html/jvms-6.htm...

Python bytecode on the other hand is not standardized: its bytecode is considered an implementation detail of CPython and can vary from version to version.

Your example reinforces my point.

Re:Why I wrote a book about interpreters by z92 on Thursday December 01, 2016 @08:56PM (#13085342)
But javac doesn't run it. It's run by "java". Therefore javac is called the compiler.

If things were such that "java" runs all .java files and creates those .class files as bytecode cache, then java won't have been called a compiler.

And similarly, if python had two different programs, one to create *.pyc files and the other runs it, the former one would have been called a python compiler.