It baffled me too, but as long as it works, and all my wanted CPAN modules work on it, why would I doubt? (a little stripped:)

Linux 2.6.37.6-35-desktop/#1 HP EliteBook 8540p Core(TM) i5 CPU M 540 + @ 2.53GHz/2534(4) i686 3843 Mb openSUSE 11.4 "Celadon" $ gcc -dumpversion 4.5 $ gcc --version gcc (SUSE Linux) 4.5.1 20101208 [gcc-4_5-branch revision 167585] $ perl -V:.*size charsize='1'; doublesize='8'; fpossize='16'; gidsize='4'; i16size='2'; i32size='4'; i64size='8'; i8size='1'; intsize='4'; ivsize='8'; longdblsize='12'; longlongsize='8'; longsize='4'; lseeksize='8'; nvsize='12'; ptrsize='4'; shortsize='2'; sizesize='4'; u16size='2'; u32size='4'; u64size='8'; u8size='1'; uidsize='4'; uvsize='8'; $ perl -V (stripped) Summary of my perl5 (revision 5 version 14 subversion 1) configuration +: Platform: osname=linux, osvers=2.6.37.6-31-desktop, archname=i686-linux-64in +t-ld config_args='-Duse64bitint -Duselongdouble -des' use64bitint=define, use64bitall=undef, uselongdouble=define cc='cc', ccflags ='-fno-strict-aliasing -pipe -fstack-protector -I +/pro/local/include -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64', optimize='-O2', cppflags='-fno-strict-aliasing -pipe -fstack-protector -I/pro/loca +l/include' ccversion='', gccversion='4.5.1 20101208 [gcc-4_5-branch revision +167585]', gccosandvers='' intsize=4, longsize=4, ptrsize=4, doublesize=8, byteorder=12345678 d_longlong=define, longlongsize=8, d_longdbl=define, longdblsize=1 +2 ivtype='long long', ivsize=8, nvtype='long double', nvsize=12, Off +_t='off_t', lseeksize=8 gnulibc_version='2.11.3' Characteristics of this binary (from libperl): Compile-time options: PERL_DONT_CREATE_GVSV PERL_MALLOC_WRAP PERL_PRESERVE_IVUV USE_64_BIT_INT USE_LARGE_FI +LES USE_LONG_DOUBLE USE_PERLIO USE_PERL_ATOF

Enjoy, Have FUN! H.Merijn

In reply to Re^4: How to find out if it is 32bit or 64bit windows? by Tux
in thread How to find out if it is 32bit or 64bit windows? by Anonymous Monk

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.