From: already5chosen@yahoo.com   
      
   On Thu, 1 Jan 2026 19:02:49 -0000 (UTC)   
   Lawrence D’Oliveiro  wrote:   
      
   > On Thu, 1 Jan 2026 07:32:34 -0000 (UTC), Michael Sanders wrote:   
   >    
   > > On Wed, 31 Dec 2025 09:37:08 -0000 (UTC), Lawrence D’Oliveiro wrote:   
   > >     
   > >> Are there any standards for how C argc/argv are supposed to behave   
   > >> on Windows?     
   > >   
   > > Good question, some more ways to open things (that I know of), see   
   > > 2nd example for 'sort of' argc/argv...   
   > >   
   > > [examples omitted]     
   >    
   > All those are at the sending end. But what would C code see at the   
   > receiving end?   
      
   The first three cases look very simple.   
      
   1.    
   argc=1   
   argv[0]=notepad.exe   
   argv[1]=NULL   
      
   2.    
   argc=1   
   argv[0]=C:\Windows\System32\calc.exe   
   argv[1]=NULL   
      
   3.   
   argc=2   
   argv[0]=notepad.exe   
   argv[1]=C:\temp\notes.txt   
   argv[2]=NULL   
      
      
   4th case does not look like a legal C code.    
   It probably was screwed either by poster's news reader or by my   
   news reader.   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)