I've done alot of work on a CPAN module. I need comments on the APIs that I added. Would how have implemented it differently? do you see an easier or more intuitive way to arrange the parameters? different function call names? Is the quads support not portable enough between native quad perls and 32 bit perls? Is the pod not clear enough?

Specifically I need comments on http://search.cpan.org/~bulkdd/Win32-API-0.70_02/API.pm#UseMI64, http://search.cpan.org/~bulkdd/Win32-API-0.70_02/API.pm#SafeReadWideCString, and http://search.cpan.org/~bulkdd/Win32-API-0.70_02/API.pm#q. There aren't public yet, so they can still be changed. Examples of the actual quads support are in the test file v70.t and 01_Struct.t in the tarball.

The changes are also at github as individual commits, https://github.com/bulk88/perl5-win32-api.

---

---

• Are you posting in the right place? Check out Where do I post X? to know for sure.
• Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:

  <code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>

• Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
• Want more info? How to link or How to display code and escape characters are good places to start.