Re: Is this the Free-Format that we asked for?

Hi Dean,

> Being a former healthcare coder myself, I feel your pain.  My point was,
this
> code should not move forward.  It was OK when /36 and /38 code came
forward
> to bring life to the AS/400, but that was TEN YEARS AGO.  IMO, it's about
> time the forward compatibility factor stopped.  With so many midrange
> programmers learning by example from the code they maintain, the bad stuff
> won't stop until support for it is stopped.

I agree, however, I'm in the situation of making modifications to vendor
software, and trying to keep those modifications as minimal as possible so
the code is as close as possible to the vendor's. That pretty much precludes
even converting their RPG III code to RPG IV. The vendor in one case is
slowly moving towards RPG IV; in another case, the AS400 was replaced with
Perot (yes, Ross's company) Systems due to a hospital buyout (the users were
not pleased!)

> >  - Can we mix CF-specs with C-specs?
>
> Why would you want to?

I have no idea. It would depend on what limitations there are on the
CF-specs. For that matter, are they CF specs, or are they /free  /endfree
delimited statements?

Regards,
Peter Dow
Dow Software Services, Inc.
909 425-0194 voice
909 425-0196 fax


> +---
> | This is the RPG/400 Mailing List!
> | To submit a new message, send your mail to RPG400-L@midrange.com.
> | To subscribe to this list send email to RPG400-L-SUB@midrange.com.
> | To unsubscribe from this list send email to RPG400-L-UNSUB@midrange.com.
> | Questions should be directed to the list owner/operator:
david@midrange.com
> +---

+---
| This is the RPG/400 Mailing List!
| To submit a new message, send your mail to RPG400-L@midrange.com.
| To subscribe to this list send email to RPG400-L-SUB@midrange.com.
| To unsubscribe from this list send email to RPG400-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---