Interestingly, OLE::Storage does something bizarre with the byte endianness of the CLSID... For instance, in one document the CLSID of the root storage consists of the following byte sequence:

D8 F4 50 30 B5 98 CF 11 BB 82 00 AA 00 BD CE 0B

(I can see it with a hex editor.) For this, $Doc->clsid($pps)->string() returns

3050F4D8-98B5-11CF-BB82-00AA00BDCE0B

In other words, it has assumed that the CLSID consists of a little-endinan DWORD, little-endian WORD, little-endian WORD, big-endian WORD, and 6 bytes (or is it 3 big-endian WORDs?). This is a bug, IMHO. The CLSID is just a sequence of 16 bytes (no endinanness) and should be returned as such.

Regards,
Vesselin

In reply to Re^3: How to get the CLSID with OLE::Storage? by bontchev
in thread How to get the CLSID with OLE::Storage? by bontchev

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.