Home  |  Linux  | Mysql  | PHP  | XML
From:Bill Luebkert Date:Sat May 24 03:25:50 2008
Subject:Re: Win32::API source code history import into svn
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 in the process of converting ?
(Eg: INT64, DWORD64) appears to be a possible argument type, but
not a return type.

There appear to be entries for 64-bit entities in API/Type.pm that
are equated to the 'q' vrbl type, but I see no logic in API.pm
itself to handle 'q' type returns.

BCDFIKLNPS are the current return types that I found.  It's not
obvious how it handles the various types after converting them
to a number.

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).

Win32::API::Prototype would have similar problems (no 'q' type and
I don't think it can handle __cdecl calling convention).

Would be nice to have all the Win32::API stuff cleaned up, thanks
for your efforts.

> Each cpan release is tagged with the same
> scheme I saw for other Win32::* modules.
> 
> Is there something like a "devel" branch?
> Or maybe everything's considered "devel" unless tagged
> as cpan release?
> 
> - Win32::API in "trunk/" and "tags/"
>   http://code.google.com/p/libwin32/source/browse
> 
> - My announcement post on use.perl
>   http://use.perl.org/~cosimo/journal/36504
Navigate in group perl.libwin32 at sever nntp.perl.org
Previous Next




  
© No Copyright
You are free to use Anything
Site Maintained by PHP Developer
Powered By PHP Consultants