Re: Dynamic inheritance

You don't particularly need the eval to set @ISA:

  no strict 'refs';
  @{ "${package}::ISA" } = $base;
[download]

Note also that string-eval is slow (the code needs to be compiled each time), so it's worth avoiding when you can; the Spawn() call can be simply:

  $self = eval { $package->Spawn() };
[download]

.. or if you aren't using the eval() to protect against dying, even:

  $self = $package->Spawn();
[download]

Hugo

Comment on Re: Dynamic inheritance Select or Download Code

Replies are listed 'Best First'.
Re^2: Dynamic inheritance by Prior Nacre V (Hermit) on Aug 06, 2004 at 14:14 UTC
This is absolutely correct. In a more general sense, you can perform any array operation on @ISA at runtime to dynamically alter the OO hierarchy. push(), shift(), splice(), etc. all work. Regards, PN5	[reply]
Re^3: Dynamic inheritance by Anonymous Monk on Aug 06, 2004 at 20:54 UTC
I think there was something about ->can vs writes to ::ISA. So it may not work in this case.	[reply]
Re^4: Dynamic inheritance by Prior Nacre V (Hermit) on Aug 06, 2004 at 21:15 UTC
Could you elaborate on that - I'm not quite with you. The can() method is in the UNIVERSAL module and is available to all objects - so nothing special there. When you say "... writes to ::ISA ...", are you referring to manipulation of @Some::Package::ISA or something else? Regards, PN5	[reply]