Yet another effort at translating the Win32 API headers

[jcc7]

In article <e0rfim$145j$1 at digitaldaemon.com>, Stewart Gordon says...
>
>J C Calvarese wrote:
>> In article <e0n1kg$14b8$1 at digitaldaemon.com>, Stewart Gordon says...
><snip>
>>> - arcane, undocumented features, e.g.  version (STANDALONE) in Core32
>> 
>> There's a simple purpose for version(STANDALONE), but it might be controversial.
>
>The real problem is that nobody seems to know what that simple purpose is.

Firstly, I thought I answered your question about this back in 2005.

Your question: 
http://www.digitalmars.com/drn-bin/wwwnews?digitalmars.D/15262

Perhaps you missed my reply:
http://www.digitalmars.com/drn-bin/wwwnews?digitalmars.D/15265

The whole thread for context:
http://www.digitalmars.com/d/archives/digitalmars/D/15248.html


But I'll try to do a better job of explaining...


*What does version(STANDALONE) do?*

Core32 is meant to complement Phobos. 

If someone doesn't want to import std.c.windows.windows, they would compile with
the version=STANDALONE set.

The default (compiling without the STANDALONE version set) has many of the
conflicts with Phobos versioned out. 

We've tried to add "version(STANDALONE)" to all of  the statements that are also
in Phobos. DMD doesn't complain about conflicts until they are actually
mentioned in code that uses both. Some of the conflicts were found by tediously
comparing std.c.windows to the Core32 files, and other conflicts were found by
"blah conflicts with blah" error statements from DMD. I guess if I were smart
I'd come up with some sort of automated tool to find all of the conflicts once
and for all, but for now I just version out the conflicts when I become aware of
them.


*What is the future of Core32?*

(No one else has asked me this question, but I've been asking it to myself.)

It's pretty bleak. The guy who originally ported the Windows API headers 
disappeared quite a while ago.

I'd been updating the files some, but I've lost interest in updating Core32,
too. Everyone else just wants to complain about it. I haven't even been using
it. I don't think anyone really wants to use Core32. Its freckles turned out to
be carcinoma. I've thought about fixing some of the problems that have been 
accumulating, but I don't really see the point anymore.

Your new Windows API project seems to be gaining momentum. If it continues to be
productive, I don't have an interest in competing. I'd rather occasionally help
out with the new team than continue to spend time with Core32.


><snip>
>> Since SVN is a problem on your Mac, maybe you could start a project at dsource
>> and just use the Trac wiki to attach files. It's not ideal, but it's better than
>> these newsgroups (IMO). There has to be something better than attaching the
>> files to these newsgroups. The files can be decoded from the web interface, but
>> it sure slows a person down when they don't have a news reader available.
><snip>
>
>You mean I should set up some pages on the wiki on which to post files? 
>  Hmm....
>
>Stewart.

Actually, what Don is doing in the Bindings project is probably the best
solution until you get your SVN problem solved (assuming there is a fix).

jcc7