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: st: encode vs destring
From
Nick Cox <[email protected]>
To
"[email protected]" <[email protected]>
Subject
Re: st: encode vs destring
Date
Fri, 26 Jul 2013 22:32:06 +0100
-destring- was written that way; -encode- wasn't.
Does that count as a reason? Perhaps not, but the original rationale
for -destring- (I can speak confidently on this point as its original
author) was largely to correct mistaken input, i.e. string input was a
mistake and the variable(s) should be numeric.
The original rationale for -encode- was, in contrast, largely to let
users have it both ways.
Nick
[email protected]
On 26 July 2013 22:20, Sergiy Radyakin <[email protected]> wrote:
> Is there any reason why Stata command encode does not support the
> replace option, which Stata command destring does support?
> Sergiy
> *
> * 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/