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

Showing content from https://mail.python.org/pipermail/python-dev/2001-December/018850.html below:

[Python-Dev] nested scopes confusion

• Previous message: [Python-Dev] nested scopes confusion
• Next message: [Python-Dev] nested scopes confusion
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

>>>>> "TH" == Thomas Heller <thomas.heller@ion-tof.com> writes:

  >> But the performance characteristics of class vs. function is
  >> really the bottleneck of your application?  Are you sure that
  >> nested fuctions are really cheaper?

  TH> Calling a.test() takes 3.3 microseconds, and c.test() takes 3.16
  TH> microseconds.

So I 5% difference, based on a single set of measurements with one
compiler/platform/etc., is enough to go out of your way to avoid
classes?  That seems conceivable for some very small set of
applications, but not in general.

Jeremy

• Previous message: [Python-Dev] nested scopes confusion
• Next message: [Python-Dev] nested scopes confusion
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

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