The Win32::API module is a nice bit of technology but can be a bit desperate to use. Its not very perl-like. (e.g. you have to pre-allocate strings before passing into the API)

IMHO, there is a nice chunk of work for people to do in adding Win32 support to standard CPAN modules using the Win32::API stuff.

This would allow:

• Most people stay away from the pain which is Win32::API
• More scripts written to use 'standard' CPAN modules "just work" on Win32 because the support is in the module
• Err...thats it

So if you do something funky with the API, consider how it might be rolled into an existing CPAN module and/or provide the same interface.

Oh...and one thing which might help regarding functions in modules is mentioned in the WIn32::API docs themselves. 'Quick View' on a DLL will show you which functions are exported.

This isn't ideal since you still need to leaf through DLLs (kernel32.dll has most things I need) and also for some reason you can't copy + paste from the Quick View, so you can't get the information out of the tool.

Rant rant. There is a Windows NT tool to extract the information I need. It doesn't let me export this information in a usable format. That sucks.

---

---

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