> Reason I'm not using an include is simple. The file does not contain
any
> variables, it just has a line of text that is & delimited. I guess I
was
> just looking at the include() method as insecure. I can see how it
> wouldn't
> be now.
Why not create your .ini file in the same format as php.ini and use
parse_ini_file() to read it. This will allow you to put in comments and
name the variables so that when someone else sees this file or tries to
edit your program, they'll know what the heck this file is.
;Host
host = localhost
;User
user = john
;Password
password = mypass
Then in PHP:
$var = parse_ini_file("/path/to/filename.ini");
echo $var['host'];
echo $var['user'];
echo $var['password'];
etc...
www.php.net/parse_ini_file
Letting a native PHP function handle reading and loading the file into
variables will be faster than a homegrown method from within PHP.
---John Holmes...
--
PHP General Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php
