"old" WinExec API appears to be what ooRexx is currently using in RxWinExec -
what API are you thinking of using in its place? How long before a
decision is made to no longer support Win95 (where WinExec
Unfortunately, I was a bit overly
optimistic about having this return the process id. It doesn't appear
that API gives you any access to the created process.
On 10/28/05, firstname.lastname@example.org <email@example.com > wrote:
Hope beyond all hope - does
this new native function return the Process ID??????
Well, with the new native
function interface, this function just does this:
On 10/28/05, Michael Lueck <firstname.lastname@example.org> wrote:
Fri, 28 Oct 2005 08:10:42 -0400, Rick McGuire wrote:
does is pass back the return code from the WinExec API. If
the value is greater than 32, then the function worked. Less
than 32 is an error return code.
dua!!! Have to set the Rexx RC
first, then return valid function to keep the
interpreter happy. I
see it now!!! Man I like Rexx w/ plain and simply "return
foo" and it
does it! ;-) C has to make things sooooo complicated!
Lueck Data Systems
This SF.Net email is sponsored by the JBoss Inc.
Today * Register for a JBoss Training Course
Free Certification Exam
for All Training Attendees Through End of 2005
Visit http://www.jboss.com/services/certification for more