Hi Nick,
The issue is that AlphaO3CPU never has the
DEFINE_SIM_OBJECT_CLASS_NAME() macro called on it because the
BEGIN_DECLARE_SIM_OJBECT() macro was never called on it. You could do
this, however it could cause other problems. DerivO3CPU should work
just fine, it's not a temporary creat
The linker gives the error.
Does a C++ object have to have a python class associated with it to
be used as a SimObjectParam? I think this may be the issue as I did
not create an AlphaO3CPU python object.
What would be the best way to go about passing references to either
an AlphaO3CPU or
There's no intentional restriction... that ought to work. It's probably
some subtle C++ template thing. Do you get the error from the compiler or
from the linker?
Steve
On 7/2/07, Nicolas Zea <[EMAIL PROTECTED]> wrote:
Are there any limitations on what objects can be used as
SimObjectParams?
Are there any limitations on what objects can be used as
SimObjectParams? For my case, I want to pass an AlphaO3CPU pointer
to another object I constructed through the python configurations.
Originally I had:
SimObjectParam *> thecpu
as my parameter definition, but this gave an error comp
