<div><span class="gmail_quote">On 7/29/05, <b class="gmail_sendername">Ross Paterson</b> <<a href="mailto:ross@soi.city.ac.uk">ross@soi.city.ac.uk</a>> wrote:</span>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">On Fri, Jul 29, 2005 at 06:41:23PM -0500, Brian Smith wrote:<br>> When we send it patches to fptools/libraries that change the API,
<br>> should we include a patch to increment the version number too? For<br>> example, I have a patch that adds bindings for WaitForMultipleObjects<br>> and WaitForSingleObject to the Win32 package. Should I increase the
<br>> Win32 package's version number in the patch I send?<br><br>That would be tedious -- incrementing on release seems more reasonable.</blockquote>
<div> </div>
<div>Okay. But, then how can I document that these new functions are not in Win32-1.0? I would like to say, for example "Introduced in version 1.1" in the documentation. That is what made me think that the version number needs to be bumped (only) during the first API change after a release.
</div><br>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">Note that the graphics part of the Win32 package fails under GHC.</blockquote>
<div> </div>
<div>Do you know why? I noticed that when I build Win32 using Cabal, genericWndProc and DeleteObject do not get linked correctly. I think it is a problem with "dynamic" imports. But, I don't know if it is related to the problem you are talking about.
</div>
<div> </div>
<div>- Brian</div>
<div> </div></div>