|
Indara and named indicators particular to the display file make a pretty good option D. It does involve more typing, though. Everyone that grew up in the 60s knows "M" is the thirteenth letter of the alphabet. <g> Perhaps _*because*_ I grew up in the sixties, I have trouble associating any of the other letters with numbers. My thinking is colored by having been trained in a shop where INKx was prohibited. > -----Original Message----- > From: Scott Klement [mailto:klemscot@klements.com] > Sent: Monday, March 18, 2002 4:36 PM > To: rpg400-l@midrange.com > Subject: Re: Window format clearing the remainder of the screen > > > > Sigh... not the "*INKC vs *IN03" holy war, again. > > a) *INKx is simple and to the point. KA=F1, KB=F2, etc. Not hard > at all to figure out. And it's immediately obvious what the > programmer is doing. Yes, it would've been nice if they were > called "*INK1 - *INK24", but they were limited to 2-digit > names. Yes, it would've been nice if they didn't arbitrarily > skip over *INKO. But, even with these complications, it takes > 5 minutes to learn. > > b) *IN01, *IN02... Yes, it's easy to figure out what these are when > things are working, but there's an added step when things aren't > working of verifying that *in01 is used for F1 and only for F1, > and the same for *IN02-*IN24. Is that difficult? No. But it's > one step of complication above *INKx, and provides very little > benefit. (Unless the idea of C being the 3rd letter of the > alphabet confuses you) > > c) AID bytes. This is EASILY more complicated than the two steps > above combined. It works great. And it lets you use nicely > named words like "KEY_F1" to represent your function keys. > But... it's a GREAT DEAL more complicated than the indicator > approach, and the end result is EXACTLY THE SAME. What ever > happened to "K.I.S.S."? >
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.