Evolution of Program Construction

Chris Kelleher

Administrator
Staff member
I'll put in my .02 cents....

Include files have altered program makeup & construction by providing a
way to write code once and re-use it multiple times and in multiple
places. Include files provide an avenue for consistent code re-use.
Maintenance is often a bit easier and changes are applied throughout the
system. Include files can be thought of as plug-n-play building blocks
for functions that are similar throughout your app.

Internal procedures are a much closer attempt at encapsulation and abide
more readily to the "building block" approach. They make debugging
much easier and if used properly, force the developer to think in terms
of specific functions -- Each individual task placed in its own
procedure. IPs help separate UI from business logic which has the added
benefit of code re-use. For example, another program could call an IP
from another program.

Triggers form the foundation of event-driven programming. Without
triggers, there would be nothing to capture events. Prior to triggers,
we had to deal with editing blocks. What seemed quite nice and
efficient back then, now seems clumsy by comparison.

This is all I have time for for now. I hopes this gets things going a
little!


Jay A. Martin
Galaxy Aerospace, LP
jmartin@galaxyaero.com

> -----Original Message-----
> From: Frank Z. Gligic [SMTP:zGligic@cgoCable.net]
> Sent: Monday, November 29, 1999 7:41 AM
> To: arcane@peg.com
> Subject: Evolution of Program Construction
>
> Folks,
>
> I would like to offer the following half-dozen goodies as a learning
> discussion.
>
> The Evolution:
> 1) Inline Code
> 2) Include Files
> 3) Internal Procedures
> 4) Persistent Procedures
> 5) Triggers
> 6) Super Procedures
>
> Please explain how each of the above have ?
>
> a) altered program makeup & construction
> b) contributed towards code re-usability
>
> Frank
>
> "Homework is due Moday" - Greg Higgins
>
 
Top