-
1
- #1
A recent post on here mentioned Snap as a good source code documentor - scanning for functions and so forth and putting nice headers on your code, helping identify which
function is called from where.
There is a snag though, it can't cope with really big applications - not sure of the exact limit, but it's around 1024 functions and procedures.
When I have something that complex, I make a copy of the code and then use Visual FoxPro to create a project with all my source code files listed (can be a bit of a pain to add them all!). It has a documenting wizard (based on Snap I think) that will tidy it all up.
Always work on a copy though, it will change the capitalisation of things if your not careful, and then your project won't compile anymore!
Good luck
Regards
Griff
Keep [Smile]ing
function is called from where.
There is a snag though, it can't cope with really big applications - not sure of the exact limit, but it's around 1024 functions and procedures.
When I have something that complex, I make a copy of the code and then use Visual FoxPro to create a project with all my source code files listed (can be a bit of a pain to add them all!). It has a documenting wizard (based on Snap I think) that will tidy it all up.
Always work on a copy though, it will change the capitalisation of things if your not careful, and then your project won't compile anymore!
Good luck
Regards
Griff
Keep [Smile]ing
