Why are objects slower than procedural subs/data structs?

This is an archived low-energy page for bots and other anonmyous visitors. Please sign up if you are a human and want to interact.

Sol-Invictus has asked for the wisdom of the Perl Monks concerning the following question: ⭐ (object-oriented programming)

what is it that makes objects 20-50% more expensive to use?

Originally posted as a Categorized Question.

Comment on Why are objects slower than procedural subs/data structs?

Replies are listed 'Best First'.
Re: Why are objects slower than procedural subs/data structs?⭐ by Fletch (Bishop) on Feb 03, 2004 at 13:16 UTC
Method dispatch overhead. When you say `foo( $a )` whatever `foo` in the current scope is called dirrectly. When you say `$obj->bar( $b )`, then perl has to check what $obj is (a scalar holding a blessed ref? a class name), then try and call `Whatever::bar`, and if that doesn't work try `SuperWhatever::bar` . . . Granted there's some caching done, but it's more than just a simple subroutine call.	[reply] [d/l] [select]
Re: Why are objects slower than procedural subs/data structs? by pajout (Curate) on Nov 08, 2005 at 07:38 UTC
Object Methods Calls Versus Function Calls contains nicely described benchmarks. The simple reason is that it very depends on CPU-cost of subroutine bodies.	[reply]

• hippo

• erzuuli

‥ Anonymous Monks are no longer allowed to use Super Search, due to an excessive use of this resource by robots.