Re: Array index nt valid

ROTFL We're off to see the wizard......  :-)


----- Original Message -----
From: "Scott Klement" <rpg400-l@xxxxxxxxxxxxxxxx>
To: "RPG programming on the AS400 / iSeries" <rpg400-l@xxxxxxxxxxxx>
Sent: Wednesday, August 04, 2004 7:39 PM
Subject: Re: Array index nt valid


> Hi Buck,
>
> > It remains my opinion that when a program falls over with an array
> > index error, then there is a problem with the program.  Even if the
> > input file has no records.  As a consumer, I would never, ever accept
> > such a program into production
>
> I've researched many software packages, and for some odd reason, none of
> them say "Warning! Do not buy this software, it has array index errors in
> it!" in their product's sales information.  Yet, after purchasing them,
> I've found that some of them do have this error.
>
> Since I've already paid for the software, management doesn't usually think
> it's acceptable to throw it away and buy something else.  They seem to
> think that if I can work around the problem, I should.
>
> How do you convince them otherwise?  Or better yet, how do you convince
> the software manufacturer to put "Warning! My code sucks!" in their
> product literature?
>
> Also, there are occasional times when I don't notice every bug in a piece
> of software that I bought.  Some of them crop up AFTER I've put it into
> production.
>
> How do you ensure that this doesn't happen?
>
> Also, sometimes the software does something that solves a business
> problem, and does that admirably and economically.  But then, there's this
> one bug that I have to work around.  Perhaps alternative software does not
> solve the business problem as well, or perhaps not as economically.
>
> Is it realistic to expect me to dump the software just to avoid working
> around a bug?
>
>
> > and as a programmer, I would feel ashamed to let one like that out of
> > the test environment
>
> On that, I agree with you.
>
>
> > If this is working as designed, then have the author document that an
> > array index error is the expected output, and what to do when it
> > occurs.  Get that in writing, and then give that note to your
> > management, who can then decide if the author should be paid for his
> > 'work' or not.
>
> If I go to a software vendor and tell them that I've encountered an error,
> the first thing they do is talk to me like a 2 year old.  After maybe a
> day of going back & forth with their tech support, they'll tell me how to
> write my program so that I won't get the error.  They sure as hell won't
> put "It's my fault" in writing so that I can give it to my management.
>
> If they do, what will my management say?  They'll tell me to work around
> the problem.  Do you seriously think my management understands that they
> shouldn't produce this error?  Especially if the vendor has provided me
> with specific instructions to solve the problem by changing my own
> program?
>
> I just hate buying software from vendors.  It never works as well as my
> own programs do.  You never get good support or service.  It's always
> overpriced.  You never know what you're getting into until you've bought
> it and are stuck with it.
>
> I hate computers.

>