FYI, last night I completed the import of Win32::API cpan
releases into libwin32 svn.
I have several development changesets that I need
to check-in now, and I plan to do that soon(*).
That will start development towards Win32::API v0.56.
Each cpan release is tagged with the same
scheme I saw for
Cosimo Streppone wrote:
FYI, last night I completed the import of Win32::API cpan
releases into libwin32 svn.
I have several development changesets that I need
to check-in now, and I plan to do that soon(*).
That will start development towards Win32::API v0.56.
Did you work on 64-bit support i
On Sat, 24 May 2008, Cosimo Streppone wrote:
>
> Is there something like a "devel" branch?
> Or maybe everything's considered "devel" unless tagged
> as cpan release?
Yes, the trunk/ is the canonical development branch, at least if
you are the maintainer of the particular module.
If *I* wanted t
On Sat, 24 May 2008, Bill Luebkert wrote:
> I need to be able to handle an arg/return type of :
> signed/unsigned __int64
> on a 32-bit OS for some debug API calls (I assume it would be even
> more useful on a 64-bit OS, but possibly int defaults to 64 there
> making it unnecessary).
In 64-b
