I have an application that heavily uses objects. However, there are a couple
of utility modules that are used across the system. I implemented these modules
using the exporter. When I ran the profiler, I was surprised to find out that
over 20% of the time was spent in the exporter.
Is there a better way to handle utility functions? Should I be using a simple
#include? Or, should I convert these functions to objects?
Thanks.
In reply to Exporter alternative? by erabus
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |