Messages per Month
9 messages in org.apache.tomcat.devRe: Updated procrun binaries| From | Sent On | Attachments |
|---|---|---|
| Mladen Turk | May 29, 2009 4:16 am | |
| Konstantin Kolinko | May 29, 2009 5:39 am | |
| Mladen Turk | May 29, 2009 6:33 am | |
| William A. Rowe, Jr. | May 29, 2009 6:59 am | |
| Mladen Turk | May 29, 2009 7:09 am | |
| Konstantin Kolinko | Jun 12, 2009 11:14 am | |
| Mladen Turk | Jun 12, 2009 11:51 am | |
| William A. Rowe, Jr. | Jun 12, 2009 12:44 pm | |
| Mladen Turk | Jun 12, 2009 12:54 pm |
| Subject: | Re: Updated procrun binaries | |
|---|---|---|
| From: | William A. Rowe, Jr. (wro...@rowe-clan.net) | |
| Date: | Jun 12, 2009 12:44:12 pm | |
| List: | org.apache.tomcat.dev | |
Mladen Turk wrote:
Konstantin Kolinko wrote:
so -win32-x86-native, -win32-x64 and -win32-ia64 would make perfect sense.
Fine with me.
"32" in "-win32-x64" looks odd.
Right win64-x64 would make more sense.
Irrelevant.
There is no win64, but there could be. Linux and most Unicies use 64ILP architecture, where ints, longs and *'s are all 64 bits.
The "64 bit Win32 API" eg win32-x64 reflects Windows' choice to use 64P architecture; 32 bit windows ints and longs, with 64 bit pointers (e.g. including handles, etc).
Do not start notating win64 until it exists; it certainly could in the future; MS could begin shipping a 64 ILP OS. Until then, this is the same API as post-windows 3.x.