paul@392 | 1 | Displacement tables are described in various publications:
|
paul@392 | 2 |
|
paul@392 | 3 | Jan Vitek, R. Nigel Horspool:
|
paul@392 | 4 | "Taming Message Passing: Efficient Method Look-Up for Dynamically Typed Languages"
|
paul@392 | 5 |
|
paul@392 | 6 | Karel Driesen:
|
paul@392 | 7 | "Software and Hardware Techniques for Efficient Polymorphic Calls"
|
paul@392 | 8 |
|
paul@148 | 9 | Shed Skin imposes various restrictions in order to facilitate compilation to
|
paul@148 | 10 | C++:
|
paul@148 | 11 |
|
paul@148 | 12 | http://shedskin.googlecode.com/
|
paul@148 | 13 |
|
paul@148 | 14 | RPython imposes different restrictions in order to facilitate compilation to
|
paul@148 | 15 | other languages:
|
paul@148 | 16 |
|
paul@148 | 17 | http://codespeak.net/pypy/dist/pypy/doc/coding-guide.html#restricted-python
|
paul@387 | 18 | http://groups.google.com/group/shedskin-discuss/msg/3f6a4ff34561a97c?dmode=source&output=gplain
|
paul@148 | 19 |
|
paul@574 | 20 | PySonar performs whole-program analysis to deduce types and produce annotated
|
paul@574 | 21 | program summaries (apparently being a later version of the program indexer
|
paul@574 | 22 | contributed to Jython):
|
paul@574 | 23 |
|
paul@574 | 24 | http://yinwang0.wordpress.com/2010/09/12/pysonar/
|
paul@574 | 25 |
|
paul@148 | 26 | CapPython limits attribute access in order to facilitate code verification:
|
paul@148 | 27 |
|
paul@148 | 28 | http://mail.python.org/pipermail/python-dev/2008-September/082475.html
|
paul@266 | 29 |
|
paul@266 | 30 | Advocacy for limited module-level initialisation:
|
paul@266 | 31 |
|
paul@266 | 32 | http://plope.com/Members/chrism/import_time_side_effects
|
paul@290 | 33 |
|
paul@290 | 34 | A question about attributes illustrating Python's deficiencies around
|
paul@290 | 35 | compile-time error detection, met with properties dogma despite accessor
|
paul@290 | 36 | methods being genuinely appropriate in various situations:
|
paul@290 | 37 |
|
paul@290 | 38 | http://mail.python.org/pipermail/python-list/2009-November/1227265.html
|
paul@290 | 39 | http://groups.google.com/group/comp.lang.python/browse_frm/thread/c07268689549cf01/
|
paul@297 | 40 |
|
paul@297 | 41 | A discussion of how closures often obscure intent and how the use of classes
|
paul@297 | 42 | and functions is often preferable:
|
paul@297 | 43 |
|
paul@297 | 44 | http://artificialcode.blogspot.com/2009/04/python-functional-programming.html
|