Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Message-ID: <3EA763E7.4090505@verizon.net> Date: Wed, 23 Apr 2003 21:11:19 -0700 From: Tron Thomas User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.0.2) Gecko/20030208 Netscape/7.02 X-Accept-Language: en-us, en MIME-Version: 1.0 To: cygwin AT cygwin DOT com Subject: How to parse windows command line Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Authentication-Info: Submitted using SMTP AUTH at pop016.verizon.net from [4.65.3.2] at Wed, 23 Apr 2003 23:11:16 -0500 I have written a Windows application that expects a file name as a command line argument. If I compile the program with a either the Borland or Micrsoft compilers I get just the file name as the command line argument when I run the program. However if I compile the program with the Cygwin compiler I get some like the following for the command line argument when I run the program: "Directory\\Directory\\Program.exe\" Filename " This is make things akward. I'm not sure why Cygwin is doing this when other compilers don't. Does Cygwin provide an API or other strategy to deal with this scenario? -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/