Calling cURL from a procedure

[SAJ]

cURL seems to use some implicit variables not identified anywhere in the
docs. Consequently, I can't call it from a procedure because I don't
know what to expose. cURL is terrific, and I can certainly live with
mainline calls if I have to, but is there a list of these variable names
somewhere? Or have I completely misunderstood the situation?

Steve Jent

[Allodoxaphobia]

Gee. I wonder what REXX -- what curl -- and what O/S?

Oh, and what problem?

[SAJ]

Sorry -- Regina 3.3, Rexx/Curl 1.4, XP.

I do believe I mentioned the problem, namely that I don't see a way to
call cURL from a procedure.

[Allodoxaphobia]

When I messed around with curl under REXX, it was in OS/2. I invoked
it (ADDRESS CMD) and piped the output into REXQUEUE. But, as curl was
'clumsy' and my only needs were WWW access, I changed my REXX program
to invoke lynx and the project proceeded a lot more smoothly.

curl can be overkill for a simple application. As the manpage states:
"...., the amount of features will make your head spin!"

I have not since had the occasion to use curl - except at the command
line. I am unaware (unsure) that curl can be CALL'ed by REXX.

Jonesy
--
Marvin L Jones | jonz | W3DHJ | linux
Pueblo, Colorado | @ | Jonesy | OS/2 __
38.24N 104.55W | config.com | DM78rf | SK

[SAJ]

What I mean by calling cURL from a procedure is this:

Handle = CurlInit()
call MyProc Handle
...
MyProc: procedure expose CurlError.
parse arg Handle
call CurlSetopt Handle
call CurlPerform Handle

as opposed to this:

Handle = CurlInit()
call CurlSetOpt Handle etc.
call CurlPerform Handle

But the exasperating thing is that as I reworked my test case to put
together this post, it ran fine. Maybe I had left the . off the end of
CurlError, I can't say now. But I don't have a problem after all. Sorry
for the false alarm, and thanks for responding.

Steve Jent