Comments on: Qualify your commands with capture http://enoriver.net/index.php/2008/09/24/qualify-your-commands-with-capture/ computing for fun and profit Fri, 03 Feb 2012 03:42:14 +0000 hourly 1 http://wordpress.org/?v=3.3.1 By: Will http://enoriver.net/index.php/2008/09/24/qualify-your-commands-with-capture/comment-page-1/#comment-6815 Will Tue, 03 Aug 2010 03:28:27 +0000 http://enoriver.net/?p=128#comment-6815 Thanks for this. This is close to what I want to do, but your description isn't general enough. What if you have an large number of files, not just 2? How do you automate that without having very verbose code? Thanks for this. This is close to what I want to do, but your description isn't general enough.

What if you have an large number of files, not just 2? How do you automate that without having very verbose code?

]]> By: Stata: how to make sure your file exists « Economics should be open http://enoriver.net/index.php/2008/09/24/qualify-your-commands-with-capture/comment-page-1/#comment-4332 Stata: how to make sure your file exists « Economics should be open Mon, 01 Mar 2010 23:29:51 +0000 http://enoriver.net/?p=128#comment-4332 [...] http://enoriver.net/index.php/2008/09/24/qualify-your-commands-with-capture/ Leave a Comment [...] [...] http://enoriver.net/index.php/2008/09/24/qualify-your-commands-with-capture/ Leave a Comment [...]

]]> By: Gabi Huiber http://enoriver.net/index.php/2008/09/24/qualify-your-commands-with-capture/comment-page-1/#comment-5 Gabi Huiber Tue, 07 Oct 2008 01:23:15 +0000 http://enoriver.net/?p=128#comment-5 The difference is scope. Local macros live inside a given do-file; they disappear when that do-file finishes running, either because it's done or because of an error. Global macros live inside a given Stata instance. They disappear when you turn Stata off (or you explicitly drop them). If you have a project split into two do-files, where the first calls the second, then any macros that you define in the first as local macros will not be recognized by the second. Sometimes that's what you want. But other times it's useful to have the first file handle all the stuff that needs to be defined once, and just serve it to the second file. If you want to do that, you need global macros. The difference is scope. Local macros live inside a given do-file; they disappear when that do-file finishes running, either because it's done or because of an error. Global macros live inside a given Stata instance. They disappear when you turn Stata off (or you explicitly drop them). If you have a project split into two do-files, where the first calls the second, then any macros that you define in the first as local macros will not be recognized by the second. Sometimes that's what you want. But other times it's useful to have the first file handle all the stuff that needs to be defined once, and just serve it to the second file. If you want to do that, you need global macros.

]]> By: fj http://enoriver.net/index.php/2008/09/24/qualify-your-commands-with-capture/comment-page-1/#comment-3 fj Tue, 07 Oct 2008 00:52:27 +0000 http://enoriver.net/?p=128#comment-3 What is the difference between globals and macros and scalars other than the identifier? `local' $global What is the difference between globals and macros and scalars other than the identifier? `local' $global

]]> By: Steli S. http://enoriver.net/index.php/2008/09/24/qualify-your-commands-with-capture/comment-page-1/#comment-2 Steli S. Sat, 27 Sep 2008 22:20:22 +0000 http://enoriver.net/?p=128#comment-2 If you write long do file, it is likely you do it in logical blocks, and as you go along you check the outcome. I find it more useful to have global, not local macro for paths etc. If you write long do file, it is likely you do it in logical blocks, and as you go along you check the outcome. I find it more useful to have global, not local macro for paths etc.

]]>