making a big php-file out of small ones

[Anon]

Hello,
Hope someone can help me... is there a tool or some easy way (i.e. by "echoing") to produce a large php-source-code-file out of a lot of little ones... currently i am always "requiring" the seperate files... it makes it very easy to overview... but I would like to distribute my little program and it would be too "orderly" if all the functions were seperated as they currenly are... so I would like to add everything into one big file... I tried viewing the source-code using apache (.phps) but it showed me my "require"-statements and I didn't want to see them but instead the file that is required... :-)
Would appreciate if someone had a tip... Thanks

[Anon]

If you are on unix you could "cat *.php>bigfile.php" or something like that.

Otherwise, why not make a little PHP script like this (unchecked code!)
$fp=fopen("bigfile.php","w");

$fpp=fopen("firstsmallfile","r");
$data=fread($fpp,filesize("firstsmallfile));
fwrite($fp,$data);
fclose($fpp);

fclose($fp);

then stick your smallfilenames in an array, build a loop around the middle section, and away you go.

[Anon]

No... it is not as easy as this... i.e. i put my mysql_database connector in the file db.inc.php3

so...
in any given file abc.php3 i have something like this:
if($a==1) { // do something }
elseif ($a==2) { require("db.inc.php3");
// do somemore stuff}
elseif ($a==3) { // do something }
elseif ($a==4) { require("db.inc.php3");
// do somemore stuff}

the required files can themselves require other files as well (and so on and so on... I would just like to basically replace the "require("blablah.php3")"-statements with the actual files... and have the code "produced" through this replacement printed out in one big file... Thanks

[Anon]

Sounds like not such a smart idea, because you will be including code over and over again.
Anyway, you could still use my method, but you'll have to parse each file line by line to see if there is a require(), and then read the corresponding file.

Looks like you'd be better off manual cut/copy/pasting the stuff.

BTW you require files that requires files that require... can you still keep track of what uses what?

[Anon]

Sounds like not such a smart idea, because you will be including code over and over again.
Anyway, you could still use my method, but you'll have to parse each file line by line to see if there is a require(), and then read the corresponding file.

I was thinking about that... and i only wanted to use it as a last resort...

Looks like you'd be better off manual cut/copy/pasting the stuff.

OH NO! there are way too many files for me to do that... I think I would go crazy... besides... as soon as i change something in the "require-version" I would have to redo the cutting and pasting... 'cause wenn everything is in one big file... i will not be able to find my way through it grin*

BTW you require files that requires files that require... can you still keep track of what uses what?

No it is actually quite ok... it probably sounds worse than it is... :-)

Thanks! I will get to the coding and while I am at it I might as well take out all the comments... (and make it real unfriendly to "outsiders") grin