Prev: Check if a macro variable ends with another string
Next: Help in PROC compare needed.
From: Arthur Tabachneck on 6 May 2010 07:54
The following is something that Nat Wooding posted on the listserv
yesterday and asked me to repost over here.

Recently, I received a note from Tony Barr who was the developer who
started the SAS project at NCSU. As the subject implies, he recently
gave a lecture at NCSU in which he recounts how he came to be hired as
the initial developer and how some of the very basic features of what
we call SAS came into existence. For one thing, he tells of how Barry
Merrill was an early user and would often call up and ask for whacko
informats and other features that would help him read the system
records of mainframes. I had long suspected that Dr. Merrill had had
such an influence and how this has given us such a robust ability to
parse input files.

Tony's link and address are below my sig.

One caution: when I first tried to view the video, something did not
work properly. However, when I tried later, it worked well.

Nat

http://www.barrsystems.com/includes_content/about_us/the_company/SASBEGINNINGS/PlayVideo.html
or, in short form: http://xrl.us/bhj9a2

Tony Barr, President, Barr Systems, Inc.
barrsystems.com
352-491-3100
From: Andrew Karp Sierra Info Services on 7 May 2010 04:23
Here is a link from Dr. Barr's website about his history with SAS:

http://barrsystems.com/about_us/the_company/sas_history.asp


On May 6, 4:54�am, Arthur Tabachneck <art...(a)netscape.net> wrote:
> The following is something that Nat Wooding posted on the listserv
> yesterday and asked me to repost over here.
>
> Recently, I received a note from Tony Barr who was the developer who
> started the SAS project at NCSU. As the subject implies, he recently
> gave a lecture at NCSU in which he recounts how he came to be hired as
> the initial developer and how some of the very basic features of what
> we call SAS came into existence. For one thing, he tells of how Barry
> Merrill was an early user and would often call up and ask for whacko
> informats and other features that would help him read the system
> records of mainframes. I had long suspected that Dr. Merrill had had
> such an influence and how this has given us such a robust ability to
> parse input files.
>
> Tony's link and address are below my sig.
>
> One caution: when I first tried to view the video, something did not
> work properly. However, when I tried later, it worked well.
>
> Nat
>
> http://www.barrsystems.com/includes_content/about_us/the_company/SASB...
> or, in short form:http://xrl.us/bhj9a2
>
> Tony Barr, President, Barr Systems, Inc.
> barrsystems.com
> 352-491-3100

 | 
Pages: 1
Prev: Check if a macro variable ends with another string
Next: Help in PROC compare needed.