in reply to Re: the #include business
in thread the #include business
Oh, yes... My project involves a number of independent perl "daemons" that share a number of common constant values, such as database table names, hence the need for an include file.
Thanks very much for the excellent explanation. I may even be moved to drop something in the collection plate, instead of taking some out as I usually do.
|
|---|
| Replies are listed 'Best First'. | |
|---|---|
|
Re: Re: Re: the #include business
by CountZero (Bishop) on Aug 23, 2003 at 07:53 UTC |