Skip Menu |

This queue is for tickets about the Win32-API CPAN distribution.

Report information
The Basics
Id: 89468
Status: resolved
Priority: 0/
Queue: Win32-API

People
Owner: Nobody in particular
Requestors: MITHALDU [...] cpan.org
Cc:
AdminCc:

Bug Information
Severity: (no value)
Broken in: (no value)
Fixed in: 0.77



Subject: $Win32::API::DEBUG is not documented
As the title says. :)
On Mon Oct 14 06:03:17 2013, MITHALDU wrote: Show quoted text
> As the title says. :)
Why should it be documented? If you ever turn it on, every sub call to a PP Win32::API sub will generate 1-3 pages of logs in your console. It has a 2nd counterpart, controlled separately, in the C side called WIN32_API_DEBUG, which will also produce 1-3 pages of logs. It needs a recompile, and can't be runtime controlled (and shouldn't due to performance loss). The debugging code was added for authors/maintainers of Win32::API to use when debugging a problem on a remote user's installation where they can't step Perl or C code.
Show quoted text
> Why should it be documented?
Obviously it's not meant to be used in production code. It should be documented for the simple purpose of allowing people who're getting no useful output from Win32::API, while experiencing failures, to at least get some hints before having to find you.
On Mon Oct 14 12:46:02 2013, MITHALDU wrote: Show quoted text
> > Why should it be documented?
> > Obviously it's not meant to be used in production code. It should be > documented for the simple purpose of allowing people who're getting no > useful output from Win32::API, while experiencing failures, to at > least get some hints before having to find you.
In theory you should check GetLastError, but it doesnt look like $^E is preserved very much in new(). This is now a bug.
That would make sense too, but in that case i also think it should be clearly mentioned somewhere in the description to use that function. :)