A RetroSearch Logo

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

Search Query:

Showing content from https://mail.python.org/pipermail/python-dev/2015-January/137948.html below:

[Python-Dev] Why co_names? Wouldn't be simpler to just use co_consts?

[Python-Dev] Why co_names? Wouldn't be simpler to just use co_consts? [Python-Dev] Why co_names? Wouldn't be simpler to just use co_consts?Greg Ewing greg.ewing at canterbury.ac.nz
Wed Jan 28 12:21:08 CET 2015
Andrea Griffini wrote:
> Sorry if the question is naive, but why is co_names needed? Wouldn't be 
> simpler to just use co_consts?

One reason might be that keeping them separate means
you can have up to 256 names and 256 consts using
1-byte opcode arguments. Otherwise, you'd be limited
to a total of 256 of both.

-- 
Greg
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