Re: Backward compatibility to V3R2

[Douglas Handy <dhandy1@xxxxxxxxxxxxx>]

Colin,

I'm responding to Hans' post rather than yours, because your original
post hasn't shown up on my end yet.  In fact, the delay problem has
seemed much worse on my end lately -- for example, one post I made 15
hours previous to this one has not yet come back to me.  Although I
have seen a response to it.  Huh?  This has always happened some but
seems worse now.  Go figure.

>>I thought that V3R2 & V3R7 were essentially the same, but for different
>>processors (CISC/RISC)

You're not completely off base.  The parity on the OS side is
essentially V3R2 and V3R7.  For example, that is when you got things
like ALWREPCHG(*YES) on triggers, or the ability to name a source file
on CHGPF, etc.

However, the HLL compilers' parity is between V3R2 and V3R6.  Note
however, that this is still *vastly* better than V3R1.  In V3R1 you
could not even do subprocedures at all ...

>>Also are there any other issues with backward compatibility to V3R2 that I
>>should know about.

LOTS of them.  V3R7 added a ton of useful stuff.  Conditional
compilation directives, nested /Copy, floating-point fields, null
field support, null-terminated strings, varying length strings, lots
of good BIFs like %editc() or %dec(), pointer arithmetic,
Alloc/Dealloc/Realloc, and probably some other stuff I don't remember
off the top of my head.  I am all too familiar with the limitations
since I have to support a client which has not yet moved off V3R2. :(

Doug
+---
| 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
+---