C. Ng wrote:
> Hi all,
>
> Please suggest how I can understand someone else's program where
> - documentation is sparse
> - in function A, there will be calls to function B, C, D and in those
> functions will be calls to functions R,S,T and so on so forth...
> making it difficult to trace
On Fri, 15 Nov 2013 03:05:04 -0800, C. Ng wrote:
> Hi all,
>
> Please suggest how I can understand someone else's program where -
> documentation is sparse - in function A, there will be calls to function
> B, C, D and in those functions will be calls to functions R,S,T
> and so on so for
On Sat, Nov 16, 2013 at 12:49 AM, Jean-Michel Pichavant
wrote:
> If the documentation is sparse, writing the doc yourself is one way to dive
> into someone else's code. To begin with, you can stick to the function
> purpose, and for the WTF functions try to document the parameters and return
>
On Nov 15, 2013, at 6:05 AM, C. Ng wrote:
> Hi all,
>
> Please suggest how I can understand someone else's program where
> - documentation is sparse
> - in function A, there will be calls to function B, C, D and in those
> functions will be calls to functions R,S,T and so on so forth...
- Original Message -
> Hi all,
>
> Please suggest how I can understand someone else's program where
> - documentation is sparse
> - in function A, there will be calls to function B, C, D and in
> those functions will be calls to functions R,S,T and so on so
> forth... making it dif
On Fri, Nov 15, 2013 at 6:19 AM, Ben Finney wrote:
> "C. Ng" writes:
>
>> Please suggest how I can understand someone else's program
>
> Welcome to this forum!
>
> I sympathise with this query. Much of the craft of programming is in
> understanding the code written by other programmers, and learn
"C. Ng" writes:
> Please suggest how I can understand someone else's program
Welcome to this forum!
I sympathise with this query. Much of the craft of programming is in
understanding the code written by other programmers, and learning from
that experience how to improve the understandability of
