Stata The Stata listserver
[Date Prev][Date Next][Thread Prev][Thread Next][Date index][Thread index]

RE: st: Programming question.

From   "Steichen, Thomas J." <>
To   <>
Subject   RE: st: Programming question.
Date   Thu, 18 Aug 2005 13:33:55 -0400

Nick Cox writes:
> local wants_pca = inlist("`method'", "pca")
> local wants_fac = inlist("`method'", "factor")
> local wants_mca = inlist("`method'", "mca")
> if (`wants_pca' + `wants_fac' + `wants_mca') == 0 {
> 	di as err "need at least one of factor pca mca"
> 	exit 198
> }

One would need to consider ramifications of abbreviations 
of "pca", "factor", and/or "mca".  I suspect (but have not
tested) that such would lead to problems via this approach.
Abbreviations of separate options would be handled by Stata's 
parser in the expected manner.

My KISS approach (separate options) avoids these unparsed 
nested option issues and is quite Stataish (and, though suboptions,
a la graph8, have become more mainstream, I find them much
harder to punctuate correctly!).  


CONFIDENTIALITY NOTE: This e-mail message, including any attachment(s),
contains information that may be confidential, protected by the attorney-
client or other legal privileges, and/or proprietary non-public
information. If you are not an intended recipient of this message or an
authorized assistant to an intended recipient, please notify the sender by
replying to this message and then delete it from your system. Use,
dissemination, distribution, or reproduction of this message and/or any of
its attachments (if any) by unintended recipients is not authorized and may
be unlawful.

*   For searches and help try:

© Copyright 1996–2017 StataCorp LLC   |   Terms of use   |   Privacy   |   Contact us   |   What's new   |   Site index