what do you mean by "OS code" ?
Quote:
|
So i use .inc and untill my script becomes commercial i change.
|
sounds like just an extra piece of work to me. when you eventually change the file name, won't you have to test for the "hacking" you are using .inc files for in the first place?
b) you mean primarily for database security? if your connect script is not in the file you're concerned about, then they probably can't do much to your db by calling it by itself. on the other hand, a .inc file would give someone a good idea of what your db structure looks like if you're working with a db.
to each his own. however, considering this guy is "NEW" to php, you gotta agree it is definately not a good habbit for a newbie. there are books out there that tell you to make a db connection include named "connect.inc" .. really nice way to expose your db login info to the world.