in reply to Convenient way to track function calls?

It sounds like you might want to factor out some of the code into their own modules so that you can more easily track the flow. Anything that has depending on various conditions none, some or many of them can be called in various sequences raises a flag in my head.

Now, this isn't to say that it's wrong or bad or anything like that! It's just something I would feel I have to justify before I would allow it out the door.

The point behind the factorization is to find those very dependencies you're looking at. If you have a set of functions and a few doorkeeper functions through which all access comes, it's a lot easier to track things.

Plus, the less code you have in a file, the easier it is to keep the file in your head. I don't know about you, but I don't have a photographic memory.

------
We are the carpenters and bricklayers of the Information Age.

Vote paco for President!

  • Comment on Re: Convenient way to track function calls?