RE: Sequence error in MR

'old hat' was not my original term.

The primary reason why I recommend avoiding it is that there is always an
coding alternative that is easier to understand and, most likely, is
better performing.  Simply put, MR exists because the original RPG
required short SHORT "code".

AFAIK, nobody's even teaching MR anymore.  Cozzi, in his Modern RPG-IV,
(2nd ed.), gives a passing reference to matching records ("it exists") but
doesn't explain it.  The several times in my 20-year career that I've had
to maintain/fix an MR app, I've had to go back to the manuals.  As usual,
code examples are not IBM's strong suit.

Tell you what.  Get Cozzi to devote a chapter to MR, and I'll jump on the
bandwagon.

Do you still code indicators in new applications?

<g>

GA

--- "Chevalier, Rick" <Rick.Chevalier@xxxxxxxxxxxxxxx> wrote:
> Why is MR 'old hat'?  Because it has been around since the beginning of
> RPG?  If so, does that mean that all other language elements still
> hanging around from the beginning are 'old hat' also?  Is new always
> better?  Of course not.  Like it or not MR is a part of the language and
> may from time to time have a place in a developers toolbox.  It's been 6
> years since I wrote my last MR program and today I may use an SQL
> solution such as Rob gave an example of if confronted with the same
> situation.  That doesn't mean that I will remove MR from consideration
> when trying to solve a programming problem.  As for programmers having
> to follow behind not knowing MR processing, yes, they should learn the
> language.  Who knows, they may even like it. <grin>
> 
> Rick


__________________________________
Do you Yahoo!?
Yahoo! SiteBuilder - Free, easy-to-use web site design software
http://sitebuilder.yahoo.com