Bookmark and Share

Notice: On April 23, 2014, Statalist moved from an email list to a forum, based at statalist.org.


[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: do, nostop issues was st: Features for Stata 14


From   László Sándor <[email protected]>
To   [email protected]
Subject   Re: do, nostop issues was st: Features for Stata 14
Date   Tue, 3 Sep 2013 16:37:44 -0400

Thanks, guys, I know.

But when I write my analysis code, it just does not feel right to
encapsulate the whole do file into something like this.

In any case, I still don't understand the pattern what crashes even
-do, nostop- and what does not.

On Tue, Sep 3, 2013 at 3:40 PM, Radwin, David <[email protected]> wrote:
> To be explicit, like this:
>
> capture {
>         block of code goes here
>         }
>
>
> David
> --
> David Radwin
> Senior Research Associate
> Education Studies Division
> RTI International
> 2150 Shattuck Ave., Suite 800
> Berkeley, CA 94704
> Phone: 510-665-8274
>
> www.rti.org
>
>
>> -----Original Message-----
>> From: [email protected] [mailto:owner-
>> [email protected]] On Behalf Of William Buchanan
>> Sent: Tuesday, September 03, 2013 12:25 PM
>> To: [email protected]
>> Subject: do, nostop issues was st: Features for Stata 14
>>
>> Hi Laszlo,
>>
>> You can use capture for blocks of code and do not need to include it for
>> each line of your code.
>>
>> HTH,
>> Billy
>>
>> On Sep 3, 2013, at 2:03 PM, László Sándor <[email protected]> wrote:
>>
>> > Richard, sure, capture would help, but I cannot add -capture noisily-
>> > to all my lines?! (OK, there are surely lines where it is genuinely
>> > foolish to proceed after an error, but I argue that for a batch of
>> > analysis there are plenty of situations where we could proceed
>> > safely.)
>> >
>> > I don't even understand why -do, nostop- does not always do the trick,
>> btw.
>> >
>> > Thanks!
>> >
>> > On Tue, Sep 3, 2013 at 3:43 PM, Richard Williams
>> > <[email protected]> wrote:
>> >> At 01:34 PM 9/3/2013, László Sándor wrote:
>> >>
>> >>> And I could also imagine some more gracious error handling. Sometimes
>> >>> not even -do, nostop- works for me, and my long jobs in batches crash
>> >>> because of a single subgroup of outcome variable I was looping over
>> >>> produced something weird for some command. I would still be interested
>> >>> in the rest of the output...
>> >>
>> >>
>> >> Will -capture- help with such situations?
>
>
> *
> *   For searches and help try:
> *   http://www.stata.com/help.cgi?search
> *   http://www.stata.com/support/faqs/resources/statalist-faq/
> *   http://www.ats.ucla.edu/stat/stata/

*
*   For searches and help try:
*   http://www.stata.com/help.cgi?search
*   http://www.stata.com/support/faqs/resources/statalist-faq/
*   http://www.ats.ucla.edu/stat/stata/


© Copyright 1996–2018 StataCorp LLC   |   Terms of use   |   Privacy   |   Contact us   |   Site index