On Jul 23, 2006, at 12:45 AM, Andreas Grau wrote: >

I vote for leaving it in the file It is part of the documentation, pod's are invented and used for reason, and people wanting to dig deeper into things need it

OK - one vote for leaving it in :)

Personlly, I can't see why it should be difficult to wait with
changing until one sees a =cut People obviously read the file and then spontaneously decide to change the file Difficult ? Yes ! Difficult people ! ;-)

Well, the problem is, if you don't know how pod works, the examples
embedded in the pod may seem like what you're actually supposed to
change - here's an example:

[snip]

 =head2 @ALLOWED_IP_ADDRESSES

 You can block anyone from using any list control panel by
 specifying exactly what IP addresses are allowed
 Leave the
 @ALLOWED_IP_ADDRESSES blank:

     @ALLOWED_IP_ADDRESSES = qw();

 to disable this security measure


 To add an address, just list it, like this:

     @ALLOWED_IP_ADDRESSES = qw(123
456
67
678
                                215
234
56
9
                                783
456
9
2);

 =cut

 @ALLOWED_IP_ADDRESSES = qw()
     unless scalar @ALLOWED_IP_ADDRESSES;

 =pod

[/snip]

Now, it is sort of trick to understand which, "@ALLOWED_IP_ADDRESSES"
I'm supposed to change Without the pod, it would just look like this:

[snip] @ALLOWED_IP_ADDRESSES = qw() unless scalar @ALLOWED_IP_ADDRESSES; [/snip]

Here's another problem, if you're reading the pod embedded, and
trying to change a variable, sometimes the formatting of the pod
itself gets in the way, example pod:

[snip]

 =head2 $ARCHIVE_DB_TYPE

 Similar to $SUBSCRIBER_DB_TYPE, I<$ARCHIVE_DB_TYPE> refers to  

what database type you'd like to be using for Dada Mail's archives The default is B, which refers to the DB File format (The Berkeley DB_File
format)

 Available also are B<MySQL> and B<PostgreSQL>


 Set $ARCHIVE_DB_TYPE to B<MySQL> for Mysql, B<PostgreSQL> for  

Postgres

 If you do use a SQL database, you most likely have to tweak
 the B<%SQL_PARAMS> hash


 =cut

 $ARCHIVE_DB_TYPE  ||= 'Db';

[/snip]

I had a report that someone set, $ARCHIVE_DB_TYPE to:

$ARCHIVE_DB_TYPE ||= B<MySQL>

Which is totally wrong, but it's exactly what the pod says