Win32 headers: Problem with COM interface indirection levels

[jcc7]

== Quote from Stewart Gordon (smjg_1998 at yahoo.com)'s article
> "jcc7" <technocrat7 at gmail.com> wrote in message
> news:f9f7oc$2ovj$1 at digitalmars.com...
> <snip>
> > It's been mentioned on the wiki page at
> > http://www.prowiki.org/wiki4d/wiki.cgi?WindowsAPI, but I think you're
> > right that
> > it's not in the "Translation instructions" section (and it probably should
> > be there).
> >
> > I get the feeling that the WindowsAPI page at Wiki4D has gotten way too
> > big to be
> > efficient. I think that it should probably be split into subpages, but I
> > would be
> > afraid of stepping on the toes of the WindowsAPI team by doing it myself.
> It probably could be split, though I'm not sure what would be the best
> approach.
> > (Also, I wonder if it would work better to store the content that's
> > current at
> > Wiki4D in the bindings wiki instead
> > [http://www.dsource.org/projects/bindings],
> > since it is part of the bindings project and dsource wikis have a cool way
> > of
> > formatting D source code.)
> <snip>
> Maybe that would be a good idea.  I haven't used Dsource's wiki engine
> much - how does it compare to prowiki?  At least it seems able to show
> arbitrary versions of  a page like MediaWiki, rather than just the current
> version and the most recent edit.

If you click on the "Archive" link, it will show you more versions, but you're
right that Trac does keep track of edits more thoroughly.

As you noticed, Trac keeps all of the version of a file as it's changed (and it
always keeps track of who changed it, too). On the other hand, I haven't quite
been able to figure out how often ProWiki saves a version in the archive or even
if they're saved permanently. And with ProWiki, it can be difficult to determine
who changed what.

Trac is really good at formatting D code automatically (for an example, see:
http://www.dsource.org/projects/tutorials/wiki/PrintfExample). By the way, the old
formatter that I had worked on has been replaced with a much cooler formatter that
is Pygments-based.

Trac allows you to get an RSS feed of project events (such when people change wiki
pages and when SVN changes are committed). ProWiki will also give an RSS feed
(which I think will even let you restrict your news to a particular page), but I
think it's helpful to have the SVN changes and the wiki changes in the same feed.
(I've been using RSS to watch that no one is being mischievous in the Tutorials
project for a while.)

Also, every wiki engine seems to have it's own flavor of wiki syntax, of course,
but you probably already realized that.

I think that using the Trac wiki pages would make more sense that using the
ProWiki page. It probably would take a little time to change the pages from
ProWiki syntax to   Trac wiki syntax, but I don't think it'd be that bad. And you
wouldn't have to change all of the content at once. You could move one section of
the page, then delete it from ProWiki, and so on. I'd even help you if you want.