Two things.

1: It sounds like you're already using a command-line program (in this case, it's curl.exe). Is that true? If so, why not create a .CMD file, with a line in it like this:

  CURL.EXE --VERSION > C:\TEMP\CURL_VERSION.TXT

and then run the .CMD file instead of the curl command line. You'll get what you need in a file, and you won't have to convince Daniel that you can't do without this extra code.

2: curl *is* open source... You're welcome to maintain your own version (continuously patching the real version with your necessary change) that acts how you want.

Hope that helps,
- Kevin

-----Original Message-----
From: David Byron
Sent: Thursday, September 18, 2003 11:26 AM

I guess this is a bit complicated, but simpler than the many pages of
Windows API code I'll need to wade through to do it another way. Yes, MSDN
has example code. Yes, it's not rocket science. Maybe it just comes down
to personal preference, but I thought I'd try to avoid it.

> I don't think the use case "I write a program that wants to
> check the curl version and I can't use a normal system call
> to fetch stdout" is very common.

Probably not. Not sure I can be more convincing than to say it would help
me out and if it doesn't cause anyone more grief, I'd love to see it. Yes,
it's more code to maintain and probably increases code size and memory usage
very slightly. For me, it's less code and less code size increase overall
(in curl + my app) than the alternative.

-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
Received on 2003-09-18