demerphq wrote:
Personally I dont see the issue. The module explains in detail about
this subject so i cant see people using it having a problem. Its not
like its going to be randomly loaded into someones namespace without
them knowing.
---
Another problem with adding TieRegistry is tha
On 1/31/06, Reini Urban <[EMAIL PROTECTED]> wrote:
> 2006/1/31, demerphq <[EMAIL PROTECTED]>:
> > On 1/31/06, Reini Urban <[EMAIL PROTECTED]> wrote:
> > > 2006/1/31, demerphq <[EMAIL PROTECTED]>:
> > > > IMO we should be bundling some of the base modules from the libwin
> > > > distro in core. Win3
2006/1/31, demerphq <[EMAIL PROTECTED]>:
> On 1/31/06, Reini Urban <[EMAIL PROTECTED]> wrote:
> > 2006/1/31, demerphq <[EMAIL PROTECTED]>:
> > > IMO we should be bundling some of the base modules from the libwin
> > > distro in core. Win32API::File being one of them, along with
> > > Win32API::Regi
On 1/31/06, Reini Urban <[EMAIL PROTECTED]> wrote:
> 2006/1/31, demerphq <[EMAIL PROTECTED]>:
> > IMO we should be bundling some of the base modules from the libwin
> > distro in core. Win32API::File being one of them, along with
> > Win32API::Registry and Win32::TieRegistry, Win32::IPC, Win32::Eve
2006/1/31, demerphq <[EMAIL PROTECTED]>:
> IMO we should be bundling some of the base modules from the libwin
> distro in core. Win32API::File being one of them, along with
> Win32API::Registry and Win32::TieRegistry, Win32::IPC, Win32::EventLog
> (the latter becuae we bundle *NIX specific counterp
