My own 2 cents. I think that we all agree with your statement. What I
think bothered Toby is that, when it was instituted, the installation
default "should" have been set the opposite of how it was distributed. In
short, that everything would work as it did previously UNLESS the user
decides to change the setting of the new option.
On Mon, 23 May 2011 10:10:09 -0500, Warren Schlechte
>My two cents worth.
>My suggestion is for SAS to give the user the ability to individually
>suppress warnings. So, since Toby feels that this truncation warning is
>unimportant, SAS should allow him (in his code) to suppress this
>From: John Hendrickx [mailto:john2.hendrickx@GMAIL.COM]
>Sent: Saturday, May 21, 2011 3:39 PM
>Subject: Re: Truncation Warning in V9.2
>Probably the same person who thought it would be a good idea to add a
>TOC level to proc report. Check out the ingenious code for suppressing
>2011/5/21 toby dunn <email@example.com>
>> I honestly have to wonder who the fool was that decided in SAS V9.2 to
>> a warning when you specify a length for a character
>> variable in a length statement that is shorter than the length of the
>> variable in the metadata.
>> Data One ;
>> Length Name $ 7 ;
>> Set SASHELP.Class ;
>> Run ;
>> Produces a warning....
>> Who was the fool that took away the ability to change a variables
>> without cluttering up my log with stupid warnings.
>> Toby Dunn
>> If you get thrown from a horse, you have to get up and get back on,
>> you landed on a cactus; then you have to roll around and scream in
>> "Any idiot can face a crisis-it's day to day living that wears you
>> ~ Anton Chekhov