Tweak initialization comments

This commit is contained in:
Tom Eastep 2009-08-17 10:45:46 -07:00
parent bc1dbb3d4e
commit 89a6d7e5db
9 changed files with 18 additions and 18 deletions

View File

@ -94,11 +94,11 @@ our $macro_commands = { COMMENT => 0, FORMAT => 2 };
# Rather than initializing globals in an INIT block or during declaration,
# we initialize them in a function. This is done for two reasons:
#
# 1. Proper initialization usually depends on the address family which isn't
# 1. Proper initialization depends on the address family which isn't
# known until the compiler has started.
#
# 2. The compiler can run multiple times in the same process so it has to be
# able to re-initialize all of its dependent modules.
# able to re-initialize its dependent modules' state.
#
sub initialize( $ ) {

View File

@ -301,11 +301,11 @@ sub initialize_chain_table();
# Rather than initializing globals in an INIT block or during declaration,
# we initialize them in a function. This is done for two reasons:
#
# 1. Proper initialization usually depends on the address family which isn't
# 1. Proper initialization depends on the address family which isn't
# known until the compiler has started.
#
# 2. The compiler can run multiple times in the same process so it has to be
# able to re-initialize all of its dependent modules.
# able to re-initialize its dependent modules' state.
#
sub initialize( $ ) {
$family = shift;

View File

@ -288,11 +288,11 @@ our %validlevels; # Valid log levels.
# Rather than initializing globals in an INIT block or during declaration,
# we initialize them in a function. This is done for two reasons:
#
# 1. Proper initialization usually depends on the address family which isn't
# 1. Proper initialization depends on the address family which isn't
# known until the compiler has started.
#
# 2. The compiler can run multiple times in the same process so it has to be
# able to re-initialize all of its dependent modules.
# able to re-initialize its dependent modules' state.
#
sub initialize( $ ) {
$family = shift;

View File

@ -105,11 +105,11 @@ our @rfc1918_networks = ( "10.0.0.0/8", "172.16.0.0/12", "192.168.0.0/16" );
# Rather than initializing globals in an INIT block or during declaration,
# we initialize them in a function. This is done for two reasons:
#
# 1. Proper initialization usually depends on the address family which isn't
# 1. Proper initialization depends on the address family which isn't
# known until the compiler has started.
#
# 2. The compiler can run multiple times in the same process so it has to be
# able to re-initialize all of its dependent modules.
# able to re-initialize its dependent modules' state.
#
sub initialize( $ ) {
$family = shift;

View File

@ -65,11 +65,11 @@ use constant { ROUTEMARKED_SHARED => 1, ROUTEMARKED_UNSHARED => 2 };
# Rather than initializing globals in an INIT block or during declaration,
# we initialize them in a function. This is done for two reasons:
#
# 1. Proper initialization usually depends on the address family which isn't
# 1. Proper initialization depends on the address family which isn't
# known until the compiler has started.
#
# 2. The compiler can run multiple times in the same process so it has to be
# able to re-initialize all of its dependent modules.
# able to re-initialize its dependent modules' state.
#
sub initialize( $ ) {
$family = shift;

View File

@ -45,11 +45,11 @@ our $family;
# Rather than initializing globals in an INIT block or during declaration,
# we initialize them in a function. This is done for two reasons:
#
# 1. Proper initialization usually depends on the address family which isn't
# 1. Proper initialization depends on the address family which isn't
# known until the compiler has started.
#
# 2. The compiler can run multiple times in the same process so it has to be
# able to re-initialize all of its dependent modules.
# able to re-initialize its dependent modules' state.
#
sub initialize( $ ) {
$family = shift;

View File

@ -66,11 +66,11 @@ my %rules_commands = ( COMMENT => 0,
# Rather than initializing globals in an INIT block or during declaration,
# we initialize them in a function. This is done for two reasons:
#
# 1. Proper initialization usually depends on the address family which isn't
# 1. Proper initialization depends on the address family which isn't
# known until the compiler has started.
#
# 2. The compiler can run multiple times in the same process so it has to be
# able to re-initialize all of its dependent modules.
# able to re-initialize its dependent modules' state.
#
sub initialize( $ ) {
$family = shift;

View File

@ -205,11 +205,11 @@ our $family;
# Rather than initializing globals in an INIT block or during declaration,
# we initialize them in a function. This is done for two reasons:
#
# 1. Proper initialization usually depends on the address family which isn't
# 1. Proper initialization depends on the address family which isn't
# known until the compiler has started.
#
# 2. The compiler can run multiple times in the same process so it has to be
# able to re-initialize all of its dependent modules.
# able to re-initialize its dependent modules' state.
#
sub initialize( $ ) {
$family = shift;

View File

@ -177,11 +177,11 @@ our %validhostoptions;
# Rather than initializing globals in an INIT block or during declaration,
# we initialize them in a function. This is done for two reasons:
#
# 1. Proper initialization usually depends on the address family which isn't
# 1. Proper initialization depends on the address family which isn't
# known until the compiler has started.
#
# 2. The compiler can run multiple times in the same process so it has to be
# able to re-initialize all of its dependent modules.
# able to re-initialize its dependent modules' state.
#
sub initialize( $ ) {
$family = shift;