Ben_Margolis 270001971J Visits (1144)
Greetings. I thought to offer a perspective different from the ones provided by architects and system developers. Here you will read the idiosyncratic thoughts of a technical writer.
In sniffing the Web last weekend, I found a post from somone who was just learning about EGL and who had the impression that EGL is essentially an update to Cross System Product (CSP), circa 1990.
Let me give you an analogy. In the 1960's, Macy's wanted to build a department store in Queens, New York. The plan was likened to the city's Guggenheim Museum, which was designed by Frank Lloyd Wright. The Macy's building was to be more than functional; it was to be beautiful.
The firm bought most of the land needed, but could not sway Mary Sondek, an elderly homeowner who valued her residence more than she valued the money on offer. The Sondek house stayed. Macy's built a circular structure with a notch that broke the circle. The irregularity was there to accommodate someone who had an established right; but the building itself was modern.
EGL is like a circular building with a notch that accommodates those who wrote code with a predecessor language. Some aspects of EGL are there to allow migration of programs written with CSP, VisualAge Generator, or Informix 4GL. But EGL encompasses far more than those aspects. The language was architected for consistency and has a beauty that CSP never had.
And I should know. My first exposure to software generation was on the IBM project that converted CSP into a COBOL generator. At first, I was a technical writer, asking questions like "How do you spell MVS?" Later, I became a tester and then a CSP programmer and came to know quite a lot about software generation. EGL is a far cry from the technologies that preceded it.
In blog entries, I'll clarify aspects of the language.