This issue tracker has been migrated to GitHub ,
and is currently read-only.
For more information,
see the GitHub FAQs in the Python's Developer Guide.
| Author | meador.inge |
|---|---|
| Recipients | alex, belopolsky, jcea, meador.inge, ncoghlan, rfk, rhettinger |
| Date | 2011年09月22日.14:30:20 |
| SpamBayes Score | 0.0040070447 |
| Marked as misclassified | No |
| Message-id | <1316701822.03.0.992552271867.issue11816@psf.upfronthosting.co.za> |
| In-reply-to |
| Content | |
|---|---|
I agree that 'bytecode_instructions' is a long-winded. FWIW, I have worked on or with a fair amount instruction level things and "instruction" or "instr" seem to be the established domain terminology. Here are a few examples: * Java ASM - http://asm.ow2.org/asm33/javadoc/user/index.html - Classes named 'InsnList', 'InsnNode' * PyPy - https://bitbucket.org/pypy/pypy/src/default/pypy/interpreter/astcompiler/assemble.py - class named 'Instruction' * Python - http://hg.python.org/cpython/file/a06ef7ab7321/Python/compile.c#l45 - struct named 'instr' * binutils - http://sourceware.org/git/?p=binutils.git;a=tree - structs, variables, etc ... with use of 'insn' and 'instruction' * gcc - http://gcc.gnu.org/git/?p=gcc.git;a=tree - structs, variables, etc ... with use of 'insn' and 'instruction' |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2011年09月22日 14:30:22 | meador.inge | set | recipients: + meador.inge, rhettinger, jcea, ncoghlan, belopolsky, alex, rfk |
| 2011年09月22日 14:30:22 | meador.inge | set | messageid: <1316701822.03.0.992552271867.issue11816@psf.upfronthosting.co.za> |
| 2011年09月22日 14:30:21 | meador.inge | link | issue11816 messages |
| 2011年09月22日 14:30:20 | meador.inge | create | |