A RetroSearch Logo

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Search Query:

Showing content from http://mail.python.org/pipermail/python-dev/2005-October/057312.html below:

[Python-Dev] Simplify lnotab? (AST branch update)

[Python-Dev] Simplify lnotab? (AST branch update) [Python-Dev] Simplify lnotab? (AST branch update)Michael Hudson mwh at python.net
Fri Oct 14 10:23:40 CEST 2005
"Phillip J. Eby" <pje at telecommunity.com> writes:

> Even better if the lines for a particular piece of code don't have
> to all come from the same file.

This seems _fairly_ esoteric to me.  Why do you need it?

I can think of two uses for lnotab information: printing source lines
and locating source lines on the filesystem.  For both, I think I'd
rather see some kind of defined protocol (methods on the code object,
maybe?) rather than inventing some kind of insane
too-general-for-the-common-case data structure.

Cheers,
mwh

-- 
42. You can measure a programmer's perspective by noting his
    attitude on the continuing vitality of FORTRAN.
  -- Alan Perlis, http://www.cs.yale.edu/homes/perlis-alan/quotes.html
More information about the Python-Dev mailing list

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4