|
Right on, John...! Always look forward to your posts...! jt "Have a GREAT day...! And a BETTER ONE TOMORROW~~~:-)" (sm) > -----Original Message----- > From: midrange-l-admin@midrange.com > [mailto:midrange-l-admin@midrange.com]On Behalf Of jpcarr@tredegar.com > Sent: Monday, November 12, 2001 6:48 PM > To: midrange-l@midrange.com > Subject: IBM's failure to provide AD tools > > > >From: Hall, Philip <phall@spss.com> > >> > I think ILE is one of the best things going on > >?> > the iSeries platform. > >> > >> But it took such a long time for the iSeries to catch up with the rest > of > >> the development/runtime world by having 'ILE' - none of it's concepts > are > >> unique to the iSeries, or software development, they just finally got > there. > >> _______________________________________________ > > > >And it took a long time. Bound programs, procedures and modules > >are 40+ year old concepts. > >Leif > > > I remember during the 80's that it was said that the pinnacle of > flexibility > was the ability to do dynamic calls easily. The 38 was great because you > could > do dynamic calls. > > I see the strengths of binding, However I still think the best is dynamic > calls > BEFORE you start any rebuttal, I am IGNORING performance issues. I am > only > talking about the flexibility of Having PGM A compilable whether > or not PGM > B > exists yet. > > Yes Compile time verification of Parameter Lists(ie prototypes) > is great no > doubt > about it. > > But the other platforms ONLY have the Make and binding concepts to compare > from > in most cases. > > Dynamic Calls - Not Always Bad > Bound Calls - Not Always Good. > > I still don't agree with the Service Program being bound when it's caller > is invoked. Many times the service program's > procedures may not even be called logically. I wish they would have did > the final resolution binding at "First Touch" > instead of automatically when it's caller is invoked. > > Just an opinion > John Carr > > ______________________________________________ > This message is intended only for the person or entity to which it is > addressed and may contain confidential material. If you are not the > intended recipient, any use, distribution or other action taken > in reliance > on this message is prohibited. If you received this message in error, > please contact the sender and delete the material from any computer. > > _______________________________________________ > This is the Midrange Systems Technical Discussion (MIDRANGE-L) > mailing list > To post a message email: MIDRANGE-L@midrange.com > To subscribe, unsubscribe, or change list options, > visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l > or email: MIDRANGE-L-request@midrange.com > 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.