I didn't get any response from this, so I'm resending...
ORIGINALLY From muir (ARCHIVE)
Date: Fri May 23 16:53:51 2003
To: [EMAIL PROTECTED]
Subject: updates for my module listings
I've taken a look at how my modules are listed...
* *** Operating System Interfaces, Hardware Drivers
*
* BSD::
* That is still not a good idea. As brian says, metainformation
* like that should not encoded in the module name. Also, it wouldn't
* necessarily encode *enough* information, such as whether the author
* has some recommendations to use instead of the deprecated one.
*
* Why can't the Makefile.P
* In article <[EMAIL PROTECTED]>, David Muir Sharnoff
* <[EMAIL PROTECTED]> wrote:
*
* > I propose that the Deprecated:: prefex be added to modules
* > whose use is discouraged by the module's author.
*
* that would not work. people may need the module to work
I propose that the Deprecated:: prefex be added to modules
whose use is discouraged by the module's author.
This would be an alternative to removing the module from CPAN.
-Dave
to what is
being done here:
IO::Multiplex
IO::NonBlocking
IO::Select
Event
POE
POE::Component::Server::TCP
Net::Socket::NonBlock
Net::Server::Multiplex
NetServer::Generic
The API borrows most heavily from IO::Multiplex.
BUGS
Nothing sane is done with excptional conditions. What causes them
anyway?
LICENSE
Copyright (C) 2002 David Muir Sharnoff. This module may be
used/copied/etc on the same terms as Perl itself.
they go out of scope. The "destory()" method will
cause the entire nest of them to loose all their values which will
allow them to be deallocated. Use "destory()" only if you're reading
more than one configruation file in your program.
CAVEATS
Since XYZ doesn't really understand Cisco configuration files it can't
know things that you might think it should.
For example, it doesn't know that "interface Serial0" is the same as
"int ser 0" nor even "interface Serial 0". Be very careful about where
Cisco's actually put spaces and where they don't.
No attempt has been made to make this module particularly fast or
efficient. This sort of manipulation isn't expected to be done a whole
lot.
XYZ objects don't automatically garbage collect themselves because they
are highly self-referrential.
LICENSE
Copyright (C) 2002 David Muir Sharnoff <[EMAIL PROTECTED]> This module may
be licensed on the same terms as Perl itself.
* So, how is yours different from MJD's Interpolation.pm?
It mentions tie in the documenation so people might be able to find it.
I didn't know Interpolation.pm existed. I was surprised when I couldn't
find something like it, so I figured I would provide one.
Interpolation.pm is a better in
* In article <[EMAIL PROTECTED]>, David Muir Sharnoff
<[EMAIL PROTECTED]> wrote:
*
* > *
* > * Or even better, Hash::ComputedValue ?
*
* > Hmmm. The way I think it will be used is mostly to do minor
* > transformations on values like adding commas to a number eg: 1,
*
* Or even better, Hash::ComputedValue ?
Hmmm. The way I think it will be used is mostly to do minor
transformations on values like adding commas to a number eg: 1,000.
So, how about Hash::Transforms?
-Dave
* In article <[EMAIL PROTECTED]>, David Muir Sharnoff
<[EMAIL PROTECTED]> wrote:
*
* > I would like to allocate a module name: Tie::LookupAsFunction.
*
* i'd like to see a more descriptive module name, perhaps
*
*Tie::Hash::ComputedValue
*
* or some such.
Sure, what
ace of the other.
-Dave
* On Nov 08, David Muir Sharnoff wrote:
* > I would like to allocate a module name: Tie::LookupAsFunction.
* >
* > Nothing fancy, but I couldn't find anyone else who had released it
* > as a module...
*
* Are you familiar with Michael Schwern's Tie::Math?
*
* - Kurt
Net::
SMTP::Receive bdpOo Receive via SMTP - delivery method required MUIR
Thanks,
-Dave
* I think File::RdistByRsync fits best.
Okay, done.
Please add:
File::
RdistByRsyncadpro Parse Rdist files and emulate using rsyncMUIR
The distribution is in my ftp area and will be picked up by CPAN
shortly.
Thanks,
-Dave
* > * > * ParseConfig::Rdist
* > * >
* > * > I'm happy with ParseConfig::Rdist.
* > * >
* > * > Shall I use that?
* > *
* > * Fine by me :)
* >
* > I had another idea.. How about Emulate::Rdist?
* >
* > That sounds better to my ear.
*
* It's not a question of sound. If the primary pur
*
* On Fri, Jan 04, 2002 at 10:34:11AM -0800, David Muir Sharnoff wrote:
* > * > looking for apporval of the names:
* > * >
* > * > Net::SMTP::Receive
* > * > Text::ParseRdist
* > *
* > * Text::* isn't where I'd expect to f
* > looking for apporval of the names:
* >
* > Net::SMTP::Receive
* > Text::ParseRdist
*
* Text::* isn't where I'd expect to find a module for parsing rdist distfiles.
*
* Perhaps a ParseConfig:: category would be a useful addition
*
* ParseConfig::Rdist
I'm happy with ParseConf
lude' ';'
'rsync_exclude' ';'
Rsync_options will be passed to any rsync commands called by rsync() that operate
on the
block in question.
Rsync_include and rsync_exclude will be passed to rsync with "- " prepended for
How about Server::SMTP::Receive? It could very easily
evolve into a real mail MTA, but it's not there yet.
-Dave
* On Wed, Aug 23, 2000 at 05:08:20PM -0700, David Muir Sharnoff wrote:
* >
* > I've just gone an written a module which I've called...
* >
*
I've just gone an written a module which I've called...
Net::SMTP::Receive
All it does is listen on port 25 and receive emails. You must
subclass it and provide a deliver() method to get it to do anything.
I'm not ready to release it yet... Needs documentation, testing, etc.
I'm wri
19 matches
Mail list logo
