Re: Maintaining large scale PHP applications

From: Colin McKinnon (colin.deletethis_at_andthis.mms3.com)
Date: 08/31/04 

Date: Tue, 31 Aug 2004 13:44:53 +0100

> The only way I can see of getting around the namespace issue is to prefix
> your functions and classes with something eg foo_ for project "foo",
> similar to what they do with the various library functions eg mysql_*

...which is really namespaces by the backdoor, and a purely 'optional'
approach.

I did have a look at phpXref and ctags. Problem with both of them is that
they don't seem very good at recording which class a method belongs to
(unless you do the Pear thing of putting each class in its own file...again
optional on the part of the programmer).

I guess the things I am looking for is:

1) managing dependencies - if an included file is changed, what files does
it impact upon
2) automatic documenting and syntax checking of code
3) a way of recording and managing test cases and actual tests
4) version control
(if anyone's got any suggestion of other things to add to this list of how
to make PHP scale better, then feel free to post).

I guess there's nothing available to do the job currently. If I ever get my
current free-time project completed I'll try hacking something.

Colin