Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.python > #59517 > unrolled thread
| Started by | Jean-Michel Pichavant <jeanmichel@sequans.com> |
|---|---|
| First post | 2013-11-15 14:49 +0100 |
| Last post | 2013-11-15 14:49 +0100 |
| Articles | 1 — 1 participant |
Back to article view | Back to comp.lang.python
Re: understanding someone else's program Jean-Michel Pichavant <jeanmichel@sequans.com> - 2013-11-15 14:49 +0100
| From | Jean-Michel Pichavant <jeanmichel@sequans.com> |
|---|---|
| Date | 2013-11-15 14:49 +0100 |
| Subject | Re: understanding someone else's program |
| Message-ID | <mailman.2651.1384523350.18130.python-list@python.org> |
----- 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 difficult to trace what happens to a certain > variable > > Am using ERIC4 IDE. > > Thanks. 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 values as well. It may take a lot of time depending on how good the current code is. JM -- IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.
Back to top | Article view | comp.lang.python
csiph-web