|
Chris, >My point is that unless you were in the confessional when the developer >confessed his sin of pride, you don't know what his motivation is. Uh, actually Chris, I was on a conference call last year with several individuals. One of whom was the developer/planner for date fields. Based on that conversation and subsequent ones I have had, I stand by my statements. I don't usually finger point, and since I was asked not to disclose the details of the conversation, I won't. I mean Chris, what's your point? Do you think I'm making this stuff up? Bob Cozzi Bob@RPGIV.COM www.rpgiv.com AS/400 Books: http://www.rpgiv.com/as400Books.html On Tuesday, September 09, 1997 12:39 PM, Chris Rehm [SMTP:Mr.AS400@IBM.NET] wrote: > > > > > > BobCozzi @ ibm.net > 09-09-97 06:51 AM > To: MIDRANGE-L @ midrange.com > cc: > Subject: RE: DATE fields in RPG-IV > > >The point is, the AS/400 is engineered by electrical engineers among > >others. It an be modified. "Software integrated circuits" is what John > >Sears calls it. The only reason DATE fields still perform bad is because > >the people that implemented it, or designed it are to proud of their work > >to "fix" it. You know this system and the S/38 before it has always been > > Bob, I think the above is a classic Cozzi slam. How do YOU know why they > won't change it? I would expect that whoever worked on that code might > indeed be proud of it. Now, let's suppose they get an email saying, "Bob > Cozzi says DATE types are too slow." > > Now, couldn't they possibly simply look through the reports from their > beta sites, run some timing things and decide that if there is a > performance difference it isn't enough of a problem to hold off on the 22 > other projects on their list? Maybe their feel like getting one or two > more projects done is important and that when Bob Cozzi puts in a S40 the > performance will be fine. > > My point is that unless you were in the confessional when the developer > confessed his sin of pride, you don't know what his motivation is. They > might just be busy on what they (right or wrong) feel are more important > issues. > > >I have only two AS/400's today: My original B10 (which is now a C10 or > >something like that) and a RISC model (40S or S40 or AS400 model 400 or > >other such confusing name). The C10 is in the garage with a sheet of > >plywood on it, being used as a shelf (anybody want it?) The RISC model is > >my development/production system. > > Sure, I could use a new shelf! How thick's the plywood? ;-) > > >I suppose, I could compromise on function over performance if Toronto > >would > >do two things. > > >1. Add blank line tolerance to the RPGIII compiler. > >2. Add native date datatype support to RPGIII, including ADDDUR, SUBDUR, > >EXTRACT, etc. > > >This would provide enough of an incentive to use date fields in my > > This kind of constructive criticism is useful, I think. Let them know what > you want. If they don't deliver and you take another route, it was their > fault. > > >Bob Cozzi > >Bob@RPGIV.COM > > > > > Chris Rehm > Mr.AS400@ibm.net > You have to ask yourself, "How often can I afford to be unexpectedly out of business?" > Get an AS/400. > +--- > | This is the Midrange System Mailing List! > | To submit a new message, send your mail to "MIDRANGE-L@midrange.com". > | To unsubscribe from this list send email to MAJORDOMO@midrange.com > | and specify 'unsubscribe MIDRANGE-L' in the body of your message. > | Questions should be directed to the list owner/operator: david@midrange.com > +--- +--- | This is the Midrange System Mailing List! | To submit a new message, send your mail to "MIDRANGE-L@midrange.com". | To unsubscribe from this list send email to MAJORDOMO@midrange.com | and specify 'unsubscribe MIDRANGE-L' in the body of your message. | Questions should be directed to the list owner/operator: david@midrange.com +---
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 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.