|
Not being a C/S guy, I may be wrong, but my belief system is this: A procedural program has the characteristic that the program tells the user what they can do in the order the program wants; in an event driven program, the user tell the program what to do in the order the user wants. That's why people are talking about a loop in this thread (no pun intended). A loop that waits for 'something' to happen and the program keeps processing. Unlike a procedural program where the program stops processing and waits for input from the user. The RPG logic cycle is just a way of implementing a procedural program. It will wait for user input and the program tells the user what to do. The only advantage of the logic cycle is that it would automatically (no additional code needed) read and write files and perform level breaks. The disadvantage is the extreme lack of flexibility. > -------- Original Message -------- > Subject: RE: Hmmmm.....$1 Billion > From: "Jeff Crosby" <jlcrosby@xxxxxxxxxxxxxxxx> > Date: Fri, March 04, 2005 8:26 am > To: "'Midrange Systems Technical Discussion'" <midrange-l@xxxxxxxxxxxx> > > > My limited experience is with the very under rated VARPG, > > which is entirely > > event driven. As I worked with VARPG programs on Windows it > > changed my > > regular programming style and logic. While still cycle > > driven, my 5250 programs now tend to focus on the events that > > might takle place rather than on the cycle. > > I will now show my ignorance (like you proclaimed a couple of posts ago <g>) > as well: > > 1) I too wonder why The Cycle is never compared to being event driven in > style. > > 2) I once compared The Cycle to SQL set-at-a-time updating in this forum, > wondering why SQL was so acceptable for this, yet The Cycle was considered > anathema. No response. > > -- > Jeff Crosby > Dilgard Frozen Foods, Inc. > P.O. Box 13369 > Ft. Wayne, IN 46868-3369 > 260-422-7531 > > The opinions expressed are my own and not necessarily the opinion of my > company. Unless I say so. > > > > -- > This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list > To post a message email: MIDRANGE-L@xxxxxxxxxxxx > To subscribe, unsubscribe, or change list options, > visit: http://lists.midrange.com/mailman/listinfo/midrange-l > or email: MIDRANGE-L-request@xxxxxxxxxxxx > Before posting, please take a moment to review the archives > at http://archive.midrange.com/midrange-l.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.