The trouble with warnings is that you could write them almost anywhere
on all sorts of grounds: how about more statistical warnings in
statistical software, for example?
I would take note of more warnings if and when they existed and I am
happy to believe that they would be widely welcomed.
But the trade-off between yet more work that somebody (i.e. the Stata
developers) has to do in adding warnings, work that would displace
developing other stuff that we want the company to do _soon_, no right
_now_, is very delicate.
I like the Stata philosophy that users take responsibility for finding
out and that we don't want or need little nagging warnings all the time.
Nick
[email protected]
David Kantor
Here's a suggestion to StataCorp and to anyone who writes programs
and then changes the names of programs or options or syntax.
(I've done this on at least one occasion.)
Allow the old names or syntax to continue working, but issue a
warning message alerting users to the change, whenever they are used.
For those who would object to the possible intrusion of these
messages, perhaps there could be an environmental variable to switch
this on and off.
*
* For searches and help try:
* http://www.stata.com/help.cgi?search
* http://www.stata.com/support/statalist/faq
* http://www.ats.ucla.edu/stat/stata/
