```Date: Sun, 27 Feb 2011 02:45:12 -0500 Reply-To: Paul Dorfman Sender: "SAS(r) Discussion" From: Paul Dorfman Subject: Re: Saturday Night Humor (was MAX() function over character values) Comments: To: Jack Hamilton A circular definition. "At once" is "at the same time". Cannot define time by time. On Sat, 26 Feb 2011 20:59:28 -0800, Jack Hamilton wrote: >Time is nature's way of keeping everything from happening all at once. > > >On Feb 26, 2011, at 8:14 PM, Paul Dorfman wrote: > >>> Define relevance. >> >> Being logically related to the matter at hand. >> >>> Estimate the sociological problems which might accompany the end of the >>> world. >> >> Zero. So are any other problems. Experiment: You are dead. Describe your >> problems. >> >>> http://www.netscrap.com/netscrap_detail.cfm?scrap_id=170 >> >> All contrived and convoluted, without exception. Try this, simple one, >> instead: Define time. >> >> Kind regards >> ------------ >> Paul Dorfman >> Jax, FL >> ------------ >> >> On Sat, 26 Feb 2011 20:00:46 -0500, Arthur Tabachneck >> wrote: >> >>> "Of course all this is quite irrelevant." >>> >>> Define relevance. Better yet, answer the following test question: >>> Estimate the sociological problems which might accompany the end of the >>> world. Construct an experiment to test your theory. >>> >>> If you find that you need more challenging questions, take a look at: >>> http://www.netscrap.com/netscrap_detail.cfm?scrap_id=170 >>> >>> Art >>> -------- >>> On Sat, 26 Feb 2011 18:02:43 -0600, Data _null_; >> wrote: >>> >>>> I worked on a project about 10 years ago and one of the many seemingly >>>> silly coding rules required the use of Mnemonic Operators. Now I use >>>> them exclusively because I have grown to like the way they look in my >>>> program. Since the introduction of the missing function I have mostly >>>> replaced GT .Z and NE ' ' with NOT MISSING(). >>>> >>>> Of course all this is quite irrelevant. >>>> >>>> On Sat, Feb 26, 2011 at 4:18 PM, Tom Abernathy >>> wrote: >>>>> Not only is the documentation confusing. So are the log messages. >>>>> If you code 'MAX' the log notes say '<>'. But if you code '<>' then the >>> log >>>>> notes say 'not =' and you get different results. >>>>> >>>>> >>>>> 495 data x; >>>>> 496 set sashelp.class; >>>>> 497 where 3 <> 3; >>>>> NOTE: The "<>" operator is interpreted as "not equals". >>>>> 498 run; >>>>> >>>>> NOTE: There were 0 observations read from the data set SASHELP.CLASS. >>>>> WHERE 3 not = 3; >>>>> NOTE: The data set WORK.X has 0 observations and 5 variables. >>>>> NOTE: DATA statement used (Total process time): >>>>> real time 0.01 seconds >>>>> cpu time 0.01 seconds >>>>> >>>>> >>>>> 499 >>>>> 500 data x; >>>>> 501 set sashelp.class; >>>>> 502 where 3 max 3; >>>>> 503 run; >>>>> >>>>> NOTE: There were 19 observations read from the data set SASHELP.CLASS. >>>>> WHERE 3<>3; >>>>> NOTE: The data set WORK.X has 19 observations and 5 variables. >>>>> NOTE: DATA statement used (Total process time): >>>>> real time 0.01 seconds >>>>> cpu time 0.00 seconds >>>>> >>>>> >>>>> I never code <> or ><. Not only because of this but also because which >>> means >>>>> min and which means max is not obvious to me. >>>>> >>>>> But now that haven't used an ASCII terminal connected to an IBM >> mainframe >>> in >>>>> 15 years I have started to use '^=' in place of 'not =' or 'ne'. >>>>> ```

Back to: Top of message | Previous page | Main SAS-L page