RE: Bob's letter on V5R4 RPG stuff

>Besides - don't you think that XML support will get a hell of a lot more
use than overloading?  Much as I'd like to have that support, XML is much
more important at this point in history. 

I could have better stated that I think this is a great move by the compiler
team to keep RPG programmers alive in this next generation of SOA's. 

I would have liked overloading and error throwing/catching enhancements more
than XML ones because I can use those everyday every where.  I only need the
XML related API's when I am doing web services. I must say that it was a
great political move.  I must also say that it is kinda revolutionary
because very few languages can boast XML support built right into the
compiler. 

>it differs in this respect from EVAL-CORR where the only requirement is a
name match
It is a good thing we have long names built into the compiler so when the
XML crazies get there hands on a schema we can actually map
<PurchaseOrderRequestLineItemLongDescription/> to a RPG variable :-)

Aaron Bartell
http://mowyourlawn.com/blog


-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx [mailto:rpg400-l-bounces@xxxxxxxxxxxx]
On Behalf Of Jon Paris
Sent: Wednesday, February 01, 2006 12:21 PM
To: rpg400-l@xxxxxxxxxxxx
Subject: RE: Bob's letter on V5R4 RPG stuff

 >> It is very interesting to me that this got added as a language feature
over the hundreds of other things that could have been done

The basic XML SAX support was added to COBOL in V5R3, I guess it was easier
for RPG to pick up and enhance that than to invent something completely new
like overloading.

Besides - don't you think that XML support will get a hell of a lot more use
than overloading?  Much as I'd like to have that support, XML is much more
important at this point in history.

 >> Can anybody elaborate on the path=xmlnode/name feature of the %XML bif?

It is a SAX parser.  The path just allows you to delve into the depths of
the document.  There is a very tight correlation required between the target
DS and the XML document (i.e. the hierarchy must match) - it differs in this
respect from EVAL-CORR where the only requirement is a name match.  path
allows you to "skip" bits of the document that you are not interested in e.g
Header type information at the beginning of the doc that precedes perhaps
repeating product information.

For repeating data you either use XML-INTO targeting a DS array (if the
number of elements is known and/or can be accommodated within RPG's limits)
or you use %HANDLER and your call-back routine is passed the DS (or DS
array) every time it is full (or all data has been processed).

No SOAP specifics that I know of.

Jon Paris
Partner400

www.Partner400.com
www.RPGWorld.com


--
This is the RPG programming on the AS400 / iSeries (RPG400-L) mailing list
To post a message email: RPG400-L@xxxxxxxxxxxx To subscribe, unsubscribe, or
change list options,
visit: http://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives at
http://archive.midrange.com/rpg400-l.