Re: [Boston.pm] Inheriting documentation for inherited command-line options

2004-09-09 Thread David Cantrell
On Wed, Sep 08, 2004 at 11:41:55PM -0400, Bob Rogers wrote: Uri Guttman [EMAIL PROTECTED] supershited: use strict; use warnings should be here too. Thank you; that sounds like a good idea. (Though usually my main interest in manipulating perl warnings is shutting them up in production

Re: [Boston.pm] CMS/Website creation and management tool

2004-09-09 Thread Bill Ricker N1VUX
That still leaves at least Bricolage Slash though, Biggest difference is Bricolage is workflow strong, and Slash is comment voting strong. and I know there are several others (Mason, etc). Mason is a framework to build a Portal, not a CMS system. Which are we looking for? Perl.com is

Re: [Boston.pm] CMS/Website creation and management tool

2004-09-09 Thread Peter Wood
Simon Cozens created Bryar: http://blog.simon-cozens.org/bryar/bryar.cgi He is now working on his next generation publishing tool, Feuilleton: http://feuilleton.simon-cozens.org/ On Thu, 09 Sep 2004 07:14:49 -0400, Bill Ricker N1VUX [EMAIL PROTECTED] wrote: That still leaves at least

Re: [Boston.pm] Inheriting documentation for inherited command-line options

2004-09-09 Thread Greg London
Bob Rogers wrote: I think I'm already well past that point in terms of option-parsing complexity. I have places where the command_line_options method calls SUPER::command_line_options in order to replace/rename options, so I need some way to supercede and/or rename things. got it. I had to

Re: [Boston.pm] Inheriting documentation for inherited command-line options

2004-09-09 Thread Greg London
Greg London wrote: Bob Rogers wrote: I have places where the command_line_options method calls SUPER::command_line_options in order to replace/rename options, so I need some way to supercede and/or rename things. Hey, just a random thought, but rather than building up a simple string in

Re: [Boston.pm] Guess what is wrong with this logic

2004-09-09 Thread Eric K. Olson
Well, I doubt this is what you're looking for, but it does assume that a person's home directory is named the same as their username. -Eric Kripa Sundar wrote: Hello all, I wanted to find out if an input word is a valid login name on my system or not. So, I wrote this: 16: sub warn_if_bogus {

Re: [Boston.pm] Guess what is wrong with this logic

2004-09-09 Thread Gyepi SAM
On Thu, Sep 09, 2004 at 04:03:33PM -0400, Kripa Sundar wrote: 20: warn blah blah\n if (glob(~$arg) !~ m{^ (/\w+)+ /$arg $}x); globIn list context, returns a (possibly empty) list of filename expansions on the value of EXPR such as the standard Unix shell

Re: [Boston.pm] Inheriting documentation for inherited command-line options

2004-09-09 Thread Bob Rogers
From: David Cantrell [EMAIL PROTECTED] Date: Thu, 9 Sep 2004 11:11:29 +0100 On Wed, Sep 08, 2004 at 11:41:55PM -0400, Bob Rogers wrote: Uri Guttman [EMAIL PROTECTED] supershited: use strict; use warnings should be here too. Thank you; that sounds like a good idea.

Re: [Boston.pm] Inheriting documentation for inherited command-line options

2004-09-09 Thread Bob Rogers
From: Greg London [EMAIL PROTECTED] Date: Thu, 09 Sep 2004 09:43:38 -0400 . . . A quick email to Damian with your rule search/replace/rename question might get you a quick answer. who knows, Damian might be able to tweak it while he's on a long flight somewhere. If you

Re: [Boston.pm] Inheriting documentation for inherited command-line options

2004-09-09 Thread Uri Guttman
BR == Bob Rogers [EMAIL PROTECTED] writes: BR problem. In particular, I have had to use BR no warnings 'recursion'; BR on occasion because the implementers of perl thought it sufficiently BR abnormal to be worth a warning if a particular function is ever entered BR 100 times more