Re: Simple Unix::Login module

Johan Vromans wrote: > > > I just wrote a simple Unix::Login module that simulates a Unix login > > prompt and does password validation/optional shell exec, etc. Synopsis: > > Cute. > How 'bout uploading and submitting a DSLI entry? Johan- Thanks for the note. Here's the DSLI entry for it: Na

Input - Regexp::Func - function regex manip

Hey all- So, I'm working on Regexp::Func, a module designed to do function-based regex manipulation. This is based on Perl 6 RFC 164; it's designed as a proof-of-concept and Perl 5 module to test its usefulness. The module provides three methods: m//=> match "//", $strings ... s/

Many new modules - input please

Hey all- I just recently finished rewriting an application used to modify host records. In the process, I wrote it into a completely modular form, with much reusable code. I'd like to upload this stuff to CPAN. There are several modules, but they can actually be used separately or together. So,

Musings about Module::Interface

Hey all- So, a while back I brought up a potential idea for a Module::Interface module. There was a little discussion of it, Chris Nandor had some good points about it and h2xs, but then it sort of died down. Anyways, I'm thinking about it again, mainly because I'm tired of crappy module iterfac

Request to register as a CPAN contributor

Howdy- I'd like to register with PAUSE (finally!): Name = Nathan Wiger Email= [EMAIL PROTECTED] Homepage = http://nate.wiger.org UserID = NWIGER Description of contributions: As a UNIX System and Network Admin, I've written a set of modules aimed at sysadmin tas

Registration of File::Remote namespace

Hi all- I just uploaded File-Remote-1.10.tar.gz, which is a standard perl package (Makefile.PL and everything) for the module I wrote called File::Remote. The namespace for this module seemed extremely obvious (the module provides methods for interacting with remote files) so after perusing all

Request for new File::Remote module

Hi all- I recently uploaded File-Remote-1.10.tar.gz, which is a standard Perl package (Makefile.PL and everything) for the module I wrote called File::Remote. The namespace for this module seemed extremely obvious (the module provides methods for interacting with remote files) so after perusing

Apache::Config module

Hi all- I've written a module that can parse the Apache httpd.conf config file (and in fact any Apache-like config file). It will take a set of directive like: ServerName www.mydomain.com UseCanonicalName Off And parse it case-insensitively, returning a ref to a hash: my

Re: Apache::Config module

That way, if you wanted (a) write a CGI script outside of mod_perl that used this data, or (b) wrote a custom (maybe non-web) app that used an Apache-like config file, you could get at the data quickly. Thanks, Nate Nathan Wiger wrote: > > Hi all- > > I've written a module tha

New modules

Hey all- I have a bunch of new modules I'd like to add to CPAN as both fully-functional Perl 5 modules and also prototypes of proposed Perl 6 additions: Name DSLI Description File::

One More New Module!

Oops, forgot one: Name DSLI Description Info - - Regexp::Func adpf Replace =~, !~, m//, s/// with functions Thanks again, Nate

New CPAN modules to add

Hey all- I have a bunch of new modules I'd like to add to CPAN as both fully-functional Perl 5 modules and also prototypes of proposed Perl 6 additions: Name DSLI Description File::

New modules - Text::Header, Class::Handler, HTML::ActiveLink

Hey all- I've got three new modules that I'd like to have registered on the module list if there are no objections: Name DSLI Description Class::Handler bdph Make Apache-like pseudoc

Potential module - Module::Interface??

Hey all- I've been thinking about this for a while. Even with all of the docs out there on how to construct a nice module, there's a lot of modules that have poor or inconsistent interfaces, which don't pass -T or even -w, and so on. So I was thinking: What if there was a Module::Interface that m

Re: Potential module - Module::Interface??

Chris Nandor wrote: > > Well, h2xs already creates a reasonable module framework, which I think is > just fine. If people used it, we would not have a lot of the problems we > have, and I don't see people using some external module when they won't use > h2xs. I am not necessarily opposed to the

Re: Potential module - Module::Interface??

Chris Nandor wrote: > > Maybe you and I have different definitions of stub module. It certainly > doesn't set up OOP, but perhaps it could be extended to provide default > constructors, etc., as an option to h2xs. Just in case you don't know, > here is what it does now: > > [pudge@yaz pudge]$

http://www.cpan.org/ vs. http://www.perl.com/CPAN/

Hey all- Just wondering if the difference between the "two" CPAN sites is intentional. That is, if you go to perl.com/CPAN, it looks like index.html is a much older version, 1.9 vs. cpan.org's 1.11. It's lacking the Kobe search stuff, doc pointers, etc. Anyways, just thought I'd point this out.

Simple Unix::Login module

ot;) || die "Sorry, you don't know your own password. Late!\n"; Is there any interest in this for the module list? I like it, but I'm biased. :-) Cheers, Nate -- Nathan Wiger <[EMAIL PROTECTED]>| # undo Sr Sysadmin, Sun Microsystems | undo: command not found