Thomas Goerner wrote:
I had a STATA question, and maybe the answer is simple.
When creating multiple programs and subprograms (via program define)
within the same .do file Stata does not list the actual command that it
is currently processing in the Results Window. This is as opposed to
programming without -program define- but "sequentially" (for lack of
better word). This obviously makes finding bugs more tedious.
Richard Williams commented:
* There is always -set trace on-. This can overwhelm you with output,
but can be quite useful when you are trying to see what specifically
caused an error.
---------------------------------------------------------------------
To avoid being overwhelmed with trace output, you can:
set tracedepth 1
I always use that initially when debugging, and I wish I could:
set tracedepth 1 , permanently
but that is not (yet?) possible.
Svend
________________________________________________________
Svend Juul
Institut for Folkesundhed, Afdeling for Epidemiologi
(Institute of Public Health, Department of Epidemiology)
Vennelyst Boulevard 6
DK-8000 Aarhus C, Denmark
Phone, work: +45 8942 6090
Phone, home: +45 8693 7796
Fax: +45 8613 1580
E-mail: [email protected]
_________________________________________________________
*
* For searches and help try:
* http://www.stata.com/support/faqs/res/findit.html
* http://www.stata.com/support/statalist/faq
* http://www.ats.ucla.edu/stat/stata/
