Re: Module naming and a couple other questions

2012-09-22 Thread Buddy Burden
Joshua, > 2. It sounds like given the single function and it's relative uniqueness, > there's no problem exporting it by default other than not being able to change > it later. For the sake of forward compatibility, I'll probably just put it in > @EXPORT_OK and require its explicit import. Beari

Re: Module naming and a couple other questions

2012-09-22 Thread Joshua Megerman
Thank you for your replies - here's a bit more info: 1. This is not something that only runs on Win32; in fact, I doubt it will run on Win32, as this uses the WMI code from the Samba project to support WMI on non-Win32 platforms. WMI is Windows Management Instrumentation (or something like tha

Re: Module naming and a couple other questions

2012-09-15 Thread Eric Wilhelm
Hi Josh, # from Joshua Megerman on Friday 14 September 2012: >My initial inclination was to just call the >module WMIClient, but I'm starting to think that WMI::Client or some >other name would be better. The only 2 modules I currently see on >CPAN that provide similar functionality are DBD::WMI

Re: Module naming and a couple other questions

2012-09-15 Thread Smylers
Joshua Megerman writes: > I'm a new member of PAUSE, looking to upload my first module. Hi Josh. Thanks for sharing with the Perl community. > 1. I have developed a module that provides an XS interface to the WMI > library (libasync_wmi_lib.so) that is generated by building the Zenoss WMI > soft