Hi Timothy, I just wanted to point out that there is some prior work in the realm of a thing or two you mentioned in other modules:
Shell quoting: As you mentioned, it's a big deal. Haarg has done quite a bit of work to make this as complete as possible: https://metacpan.org/pod/Win32::ShellQuote CreateProcess: I might be off base, but maybe https://metacpan.org/pod/Win32::Daemon can help here. Outside of that, I'd likely continue in the vein of Win32::Foo for naming conventions. Thanks, Chase On Tue, Nov 13, 2018 at 12:05 PM Timothy Madden <terminato...@gmail.com> wrote: > Hello, > > For ::ShellExecute API function on Windows I got confused with the > possible names like: > > - Win32::ShellExecute > - Win32::API::ShellExecute > - Win32API::ShellExecute > > I noticed Win32API:: namespace mostly uses XS modules to expose the API, > while my module uses dynamic loading of .dll files with Win32::API. Some > people say this is not as good as the equivalent XS binding, though it > is not clear for me why and I much prefer pure-perl modules for > distribution / installation reasons. > > I also need some names for a couple of modules like: > > - Win32::CmdQuote::Simple, for command quoting in a safe and strict > manner, as this is a big issue on Windows > > - Win32::API::Error, for a base exception class that encapsulates the > error message and error code from ::GetLastError() > > - Win32::API::CreateProcess - there is a module available that exposes > only part of the call interface of the C function, so I would need a > more detailed module (the function argument list is rather complicated > for this one). > > I am a bit worried about the proper names as I notice Win32:: and > Win32API:: modules are included by default with the Windows version of > perl (I use Strawberry). I also believe there is a need for more API > functions exposed in the language for the Windows platform. > > Any suggestions appreciated, > > -- > Thank you, > Timothy Madden >
