D issues are now tracked on GitHub. This Bugzilla instance remains as a read-only archive.
Issue 5614 - version(Win32) vs version(Windows) in Phobos
Summary: version(Win32) vs version(Windows) in Phobos
Status: RESOLVED FIXED
Alias: None
Product: D
Classification: Unclassified
Component: phobos (show other issues)
Version: D2
Hardware: x86_64 Windows
: P2 normal
Assignee: No Owner
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-02-19 08:23 UTC by Richard Webb
Modified: 2012-01-21 18:41 UTC (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this issue.
Description Richard Webb 2011-02-19 08:23:08 UTC
If you try to compile various things in Phobos using -m64 on Windows, you get various build failures which appear to be down to various std files doing things in version(Win32) blocks, when 64bit builds only define 'Win64'.

e.g.

line 28 of std.file imports various things for version(Win32), but later tries to use those imports in version(Windows) blocks.


std.__fileinit declares and sets up 'useWfuncs' in a 'Win32' block. In this case, can it be assumed that the Wide functions are always present in 64bit builds?


std.system sets 'Family' to Win32 in 32bit builds, and asserts in 64bit builds. I'm not sure if this needs a Win64 family or not?


std.stream, std.mmfile, and std.c.stdio all have similar issues.


I know that 64bit support on Windows is some way off, but it would be nice if the front end stuff built at least.
Comment 3 Jonathan M Davis 2012-01-21 18:41:51 UTC
Okay. That automatic posting to bugzilla from github bit is definitely cool.