Hi,
There are many things I don't understand about my Vista64 box - and this is one of them.
I have both x86 and x64 builds of ActivePerl 5.12.2 (build 1202), and I have this minimal script:
use warnings; use Win32::TieRegistry; my %Registry; use Win32::TieRegistry ( TiedHash => \%Registry ); print "$_\n" for keys %{$Registry->{LMachine}{SOFTWARE}};
I don't understand why that script produces one list of keys when I run it using the x86 build, and a different list of keys when I run it using the x64 build. Some keys appear in both lists, other keys in just one list or the other. Why is that ?

Both perl builds have the same versions of Win32API::Registry (0.30) and Win32::TieRegistry (0.26), and I'm running (as Administrator) both perls in the System32/cmd.exe shell.

Cheers,
Rob

In reply to Win32::TieRegistry surprises by syphilis

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.