I doubt that reblessing a Win32::OLE object will work as you intend it to, because Win32::OLE objects live mainly in C/XS space. I recommend you aggregate the WMI object instead of trying to extend it, and delegate all unknown methods to the WMI object via AUTOLOAD:

sub AUTOLOAD {
    my $self = shift;
    (my $meth = $AUTOLOAD) =~ s/.*::/;

    # Now call the method on the WMI object
    $self->{wmi}->$meth(@_);
}

[download]

The above method could be refined further to play with the stack so that all error messages point to the real caller instead of the reflection method, but for a first stab, this approach is OK.

In reply to Re^3: Is it a reference issue or what? by Corion
in thread Is it a reference issue or what? by OzVegan

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.