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

2004-09-11 Thread Kripa Sundar
Dear Uri, from perlop: A (file)glob evaluates its (embedded) argument only when it is starting a new list. All values must be read before it will start over. [...] i call that documented :) I am forced to agree. :-) KS If I want to grok ~someone/some/stuff, glob()

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

2004-09-11 Thread Bob Rogers
From: Uri Guttman [EMAIL PROTECTED] Date: Fri, 10 Sep 2004 01:37:14 -0400 BR == Bob Rogers [EMAIL PROTECTED] writes: BRBut this morning, I had an idea for Pod::CLOD while showering. BR (That's a good sign; some of my best ideas come to me in the shower.) so you aren't

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

2004-09-11 Thread Bob Rogers
From: Greg London [EMAIL PROTECTED] Date: Thu, 9 Sep 2004 23:00:24 -0400 (EDT) Bob Rogers said: Seriously, splitting up the options this way does make it easier to combine them, but it still requires globals to store the values, and as long as that's true, I find it hard

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

2004-09-11 Thread Uri Guttman
BR == Bob Rogers [EMAIL PROTECTED] writes: BRThe Parse sub is a prime example of what I would consider BR counterproductive code decoration. It violates the first rule of BR commenting, namely that comments should say something about the code BR that is not obvious: as i said, i am