in reply to Re^4: length of pack 'J' and Win64/Win32 C data type model, pointer length, DWORD_PTR
in thread length of pack 'J' and Win64/Win32 C data type model, pointer length, DWORD_PTR

afaik you'd have to do some non-trivial hacking.

Absolutely. I tried it once.

We complain about the current 2106 warnings that the "successful build produces, you should see what happens when you try adding a few __int64 #defines/typedefs to the equation. Working what to change is impossible.

Don't ya just love theoreticians :)


Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.
"Science is about questioning the status quo. Questioning authority".
In the absence of evidence, opinion is indistinguishable from prejudice.
RIP an inspiration; A true Folk's Guy
  • Comment on Re^5: length of pack 'J' and Win64/Win32 C data type model, pointer length, DWORD_PTR
  • Download Code

Replies are listed 'Best First'.
Re^6: length of pack 'J' and Win64/Win32 C data type model, pointer length, DWORD_PTR
by syphilis (Archbishop) on Nov 08, 2010 at 10:30 UTC
    Working what to change is impossible

    Yes, that was my feeling too after both of my attempts to build such a Win32 perl.

    I expected that the task should be much simpler now that the perl source has 64-bit config and config_H files in the win32 folder but, although they do the job for 64-bit builds, I was unable to coerce them into helping provide 64-bit integer support for 32-bit builds. (This could well be nothing more than ignorance on my part.)

    Cheers,
    Rob
      I was unable to coerce them into helping provide 64-bit integer support for 32-bit builds. (This could well be nothing more than ignorance on my part.)

      Well, if you couldn't work it out, I know I shalln't be trying again. And I doubt many others will.