Early days of Clipper

Notes on early days of Clipper

Some quotations :

Clipper was originally built in 1985 as a compiler for dBASE III.

Clipper was built by Nantucket Corporation led by Barry ReBell (management) and Brian Russell (technical), and  later sold to …

Source

         ~~~~~~~~~~~~~~~~~~~

Brett Oliver, Jim Warner, Brian Russell, Richard McConnell …

Main architects and primary developers of Clipper and founders of Nantucket Corporation. It was 1984 when
Clipper was born.

Source

~~~~~~~~~~~~~~~~~~~

Clipper Summer’87 Manual, “Credits” page :

ClpSum87Credits

~~~~~~~~~~~~~~~~~~~

Clipper 5.0 Manual, “Credits” page :

Clp5.0Credits

~~~~~~~~~~~~~~~~~~~

… and 30 years after birth of this phenomenal myth, one (or first) of main builders suddenly appeared : Brett Oliver !

By a comment to one page of this blog :

Not only main starter / builder of Clipper, he is also author of wonderful books :

Clipper Programming: An In-Depth Introduction to Programming

This book also is a myth.

And he told me on request, something on beginning and building story of this great myth;

Brian was working at Ashton-Tate, as was I.

I was in tech support, alongside Brian, and customers that were phoning in kept asking for a compiler.

So I approached Barry for the money to back it. He had a temp agency. I met him in the Ashton-Tate cafeteria.

I recruited Brian at lunch at a Japanese restaurant in Culver city.

Clipper was the first program Brian had written in ‘C’.

He learned C as he programmed Clipper.

I asked him when I was recruiting him if he had ever written a compiler.

He said he had written a Pascal compiler in university. (He later admitted that it had never worked!).

The first development office was a beach house in Malibu.

Tom Rettig was the editor for dNEWS at Ashton-Tate. I took over as editor of dNEWS.

I was the first VP of sales, and one of my employees was Mary Beth. I introduced her to Brian and later they married.

At the first Comdex in Vegas, Brian was upstairs in his room – coding.

He got one command to work – paint a dot on the screen. We demonstrated that one command, and showed that we could draw a box 20 times faster than dBASE.

I wrote a couple of books on Clipper, and was also on the dBASE for Windows development team at Borland. 

I worked with Tom at his condo in Santa Monica for a time. Too bad he died.

Barry died in 2009.

Brian and I went dirt biking together. He loaned me his street bike for a couple of months when my car was getting fixed. He is a good guy. I think he is working in LA.

We live in San Diego, – my wife is from Liechtenstein. We have three boys.

I am Scottish. Currently programming in eCommerce.

Anyway, nice chatting.

Stay in touch.

I wish he will write more …

Format of xBase Files

xBase File Format Description

Clipper Description

Developed by Nantucket software and released in winter of 1984, first shipping 25 May 1985.

Clipper was a typical database development language and DOS based. Originally is was used as a replacement programming language for Ashton Tate’s dbase II database environment that could be compiled and executed as a standalone application.

Millions of applications were built typically for businesses dealing with small databases like client management, stock keeping. Many applications for banking and insurance companies were developed were the application was considered too small to be developed and run on mainframes. Clipper often served as a front end exactly for the above mentioned mainframe applications and did very well in this area.

One of the language’s features: the possibility to link ‘C’ and machine language objects made it a virtual unlimited expandable environment. When you missed a feature, an interface or whatever you could program that yourself and the extension made a reusable part of your toolbox. Libraries were also made by third parties but the programmer could also create its own library or enhance the existing ones.

One of the disadvantages, for commercial developers at least, was that a clipper executable could easily be disassembled or de-compiled to produce native source code. There were even commercial packages for that. Between the manufacturers of decompilers and Clipper a covenant was agreed that with a certain code in the source the decompilers would not decompile. But for the hard core hackers no door was kept close.

Around the early 1990’s the users felt a need for a more object oriented environment. Nantucket’s answer was: Clipper 5.0 up to 5.3. This made the Clipper language more sophisticated, but completely OO it never was. Objects and classes could be created but the language needed more, and quickly, should it keep its programmers corps it had created since 1984.

Too late the Nantucket company realized it had to port the Clipper environment to the Windows platform as well and began developing a new project: Aspen: Clipper for Windows. Too late, or at least the research was not given top priority for research and development. In August 1994 (Shipped December 1995) a first version became available and was called: Clipper VO (virtual objects) It was truly windows based but had to cope with many typical first issue bugs that were not explained to the full extend. Again programmers had to build new work arounds and did not feel very comfortable with that idea.

The old stock of programmers however had already switched to Visual Basic (Microsoft) and later Delphi (Borland) This came about because many customers with small database environments wanted to upgrade to window versions in their turn pressured by their clients. And as usual clients wanted their applications yesterday!

A second reason why Clipper never got its previous user base back was that the transition to Clipper VO proved to be too complicated for many senior programmers, and juniors already learned to program in Delphi or VB and later Java.

That was a pity because VO proved to be a very powerful and sophisticated database development tool.

Though Nantucket / CA promised a high degree of compatibility with older developments this did not materialize to the degree to make life easier to former Clipper programmers. The result was that programs were rebuilt in the new environments, the best way to do porting actually. Again slimming down the market for Clipper programmers.

In 1995 Computer Associates bought up the Clipper environment, killed the Clipper DOS version and pre-matured project Aspen, and further developed VO

Other developments for Clipper:

Clipper also could be converted to run on UNIX systems by using a porting tool called Flagship. It runs suitably well.

XBase++ is an OO environment and translates DOS Clipper to Windows but does not enhance the clipper development to an event driven application.

Clip-4-Win is a 16 bit compiler and generated character based applications that ran fairly well within Windows.

Harbour  Clipper got a new life with the Harbour project.

The Harbour-project was started as an open source project in early 1999, the project is still on.

The Harbour programming language is a superset of the well known x-Base language, often referred to as Clipper. Harbour is 100% backward compatible with the Clipper Language, yet it adds many modern features and tools comparable to today’s leading compilers.

Out of the harbour-project, xHarbour (extended Harbour) was started late 2001 as a fork off of the Harbour Project

Clipper is still alive!

Chronology:

1984 first issue: Winter 1984

1990 first issue: Clipper 5.0 (distributed at DefCon fall 1990)

1994 first issue of Clipper VO

1997 Clipper VO 2.5

1999 An open source project: Harbour takes up the challenge

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Note : This post gathered from here.


dBASE and Wayne Ratliff

dBASE may be traced back to the mid 1960’s in the form of a system called RETRIEVE, which was marketed by Tymshare Corporation. RETRIEVE was used by Jet Propulsion Laboratory of Pasadena,Calif. In the late 60’s Jeb Long, a new programmer at JPL, was assigned the task of writing a program which would perform the same functions as RETRIEVE.

Back in 1973 he was a software engineer at the California Institute of Technology’s Jet Propulsion Laboratory, where he developed a file management program called JPLDIS (Jet Propulsion Laboratory Display Information System) written in FORTRAN, running in a UNIVAC 1108 mainframe. He spent over 11 years at JPL, being responsible for many of the software development tasks of USA’s space program, like the Mariner and Viking missions to Mars.

JPLDIS was the precursor of dBASE, that runs in CP/M microcomputers. Latter with Wayne Ratliff, Jeb Long translated that original version of dBASE II to run in an IBM PC. All that work was been done in assembly language.

Jeb was one of the founders of Ashton-Tate and was there for 8 years. He was known as the guru of the dBASE products at Ashton-Tate, and was the architect of the dBASE language and responsible for its components for all versions of dBASE III and dBASE IV, with the exception of the initial dBASE version.

Jeb Long is an experienced software designer and engineer. Since he left Ashton-Tate back in 1990 he has been working as an independent consultant and writer of numerous technical documents, books and articles for technical magazines, and had been working for some of the most prestigious companies at the USA

From 1969 to 1982, Wayne Ratliff worked for the Martin Marietta Corporation in a progression of engineering and managerial positions. He was a member of the NASA Viking Flight Team when the Viking spacecraft landed on Mars in 1976, and wrote the data-management system, MFILE, for the Viking lander support software.

In 1978, he wrote a database program in assembly language, at the Jet Propulsion Laboratory (JPL) in Passadena, California. He called it Vulcan (after Mr. Spock of Star Trek), that was based on Jeb Long’s JPLDIS. This program was written to help him win the football pool at the office, which he marketed by himself from 1979 to 1980. Vulcan had its ups and downs and by 1980 was in what seemed to be a permanent down state.

Ratliff was born in 1946 in Trenton, Ohio and raised in various cities and towns in Ohio and Germany. He later resides in the Los Angeles area.

In late 1980 he met George Tate, who found the product worth while and entered into a marketing agreement with Ashton-Tate and renamed the Vulcan product dBASE H. Wayne had given up trying to sell copies of it for $50 each. George told him that he thought it would sell better at $695, so they made a deal and dBASE II was the result. In mid-1983, Ashton-Tate purchased the dBASE II technology and copyright from Ratliff and he joined Ashton-Tate as vice president of new technology. Ratliff was the project manager for dBASE III, as well as designer and lead programmer.

The program was renamed dBASE II because they knew that version 1 wouldn’t sell. It originally ran on a CP/M computer and then was moved over to the IBM PC.

Note there was never anyone named Ashton, it sounded better. Ashton was a maccaw (parrot) that was the unofficial mascot of Ashton-Tate.

~~~~~~~~~~~~~~~~~~~~~~~~~~~

This article gathered from here.

A tale about Clipper

ShipSilhouette5

A tale about the origin of Clipper

There is a tale about the origin of CA-Clipper. Whether it is true or not, few people know, but “insiders” have said that it is not far from the truth. Here it is.

One day in a seafood restaurant in Malibu, California, an Ashton-Tate employee and a consultant friend were having lunch. They were expressing their annoyance at the fact that Ashton-Tate had not created a compiler for the dBase language.

The two thought that maybe they should have a go at starting up a new company to create the compiler. As the excitement grew and the ideas flew, the issue of a product name came up.

One of the two noticed a picture of a sailing ship on the napkin (after all this was a seafood restaurant). It was a clipper ship — a sleek, speedy, and elegant thing. That seemed to describe what they were trying to create.

What about the company name? The menu answered that question — the restaurant name was Nantucket Lighthouse.

And so Nantucket’s Clipper was born.

The consultant was Barry ReBell and the Ashton-Tate employee was Brian Russell.

Since that time there were four “seasonally” named versions of the compiler: Winter 85, Spring 86, Autumn 86, Summer 87. Very “California”…

These early versions clearly billed themselves as dBase compilers, with the Summer 87 version displaying “dBase III® compiler” on the floppy disks and documentation.

Many programmers using Clipper at the time were really “just” dBase programmers with a tool to create faster programs. So it was quite a shock to them when Clipper 5 was released. “What have they done to our language?”, they asked. Local variables? Code blocks? Tbrowse?

But there were also those of us who had strained against the limitations of the dBase language — the lack of modularity, the clumsiness, the vulnerability of public and private variables.

So we recognized that Clipper 5 was a turning point in the history of the Xbase language. No longer billed as a dBase compiler, Clipper became an “Application Development System”. A real language.

Well, maybe not as real as C, but getting there. In fact, many Clipper 5 concepts were borrowed from C and other languages. The increment operator (++) and expression lists, for example, seem to have come from C, while code blocks may have been inspired by SmallTalk

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

This article borrowed by courtesy of author,  from here.

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Please look at here for continuation of this post.