× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.




-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx
[mailto:rpg400-l-bounces@xxxxxxxxxxxx]On Behalf Of Tom Liotta
Sent: Thursday, May 22, 2003 2:13 PM
To: rpg400-l@xxxxxxxxxxxx
Subject: RE: threading in rpg


rpg400-l-request@xxxxxxxxxxxx wrote:

>   9. RE: threading in rpg (Walden H. Leverich III)
>
>>From: qsrvbas@xxxxxxxxxxxx [mailto:qsrvbas@xxxxxxxxxxxx]
>>...VARPG used essentially the same compiler...
>
>It's been a while since I looked at VARPG, but I don't recall is compiling
>the code for you. Syntax checking, yes, but you don't actually get a *PGM
>object you can restore to your iSeries, do you?

>The "ILE RPG compiler" didn't create *PGM objects any more than the VARPG
>compiler did. Instead, it parsed source and did all the magic to create
>something like "W-code". Then, it was/is the W-code that gets turned into
>a *MODULE object and eventually linked into the *PGM object. The "RPG
>compiler" is long gone by then.


so VARPG probably compiles the rpg code, captures the w-code, then
translates the W-Code back to C code and compiles it on the pc?

If so, is that all ibm proprietary?   Even if a developer pays the $$ for
the w-code compiler and documentation, does ibm still not provide a way to
capture the w-code that is output by its rpg and other compilers?

-Steve



As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.