Derrik Pates writes:
> passed to its methods as a reference, and it seems that every time a
> method is called, the DESTROY method also gets called (obviously NOT what
> I'm looking for).
DESTROY works a lot like a C++ destructor. If you are seeing it calling
multiple times for the "same" object, then your code is probably creating
temporary objects that refer to the same C struct (or whatever forms the
guts of your external library interface).
If you could post a small example that demonstrates your problem, I'm sure
that we can figure out a solution.
- Ken
--
Ken Fox, [EMAIL PROTECTED], (313)59-44794
------------------------------------------------------------------------
Ford Motor Company, Powertrain | "Is this some sort of trick
Analytical Powertrain Methods Department | question or what?" -- Calvin
C3P Implementation Section |
