Text Only | Text with Attachments

QB64.org Forum

Active Forums => QB64 Discussion => Topic started by: Aurel on July 06, 2021, 04:55:25 am

Title: GetCommandLine - winApi fn
Post by: Aurel on July 06, 2021, 04:55:25 am
Yo Sprigssy and others...
can i do that in qb64:

Code: QB64: [Select]
  1. Declare Function GetCommandLine Lib "kernel32.dll" Alias "GetCommandLineA" () as String
Title: Re: GetCommandLine - winApi fn
Post by: FellippeHeitor on July 06, 2021, 05:00:02 am
You don't declare an external function directly, it must be inside a DECLARE LIBRARY block.

However, for that example specifically, we already have COMMAND$

Code: QB64: [Select]
Title: Re: GetCommandLine - winApi fn
Post by: FellippeHeitor on July 06, 2021, 05:03:51 am
See examples of declaring a library at http://www.qb64.org/wiki/Windows_Libraries
Title: Re: GetCommandLine - winApi fn
Post by: Aurel on July 06, 2021, 05:28:11 am
Hi Felipe
I don't ask about using this "aka" version of api function with print than
i want invoke this function like this :

 string fname = GetCommandLine ()

then parse fname to extract just file name from full path .
is that possible with COMMAND$  ?

oK..i will look into wiki first...
Title: Re: GetCommandLine - winApi fn
Post by: Aurel on July 06, 2021, 05:40:50 am
Ah i see i need  system dll declaration using DECLARE...
( dude..that blue wiki examples killing my eyes..heh )
ok

Code: QB64: [Select]
  1.  DECLARE DYNAMIC LIBRARY "Kernel32"
  2. Function  GetCommandLineA& ()
  3.  

hmm i see two ways ,ok i will try both...

another is presented by Dav !!!

Code: QB64: [Select]
  2. Function  GetCommandLine  Alias GetCommandLineA  ()
  3.  
Title: Re: GetCommandLine - winApi fn
Post by: FellippeHeitor on July 06, 2021, 06:08:50 am
Code: QB64: [Select]
  2. FOR c = 1 TO count
  3.     a$ = COMMAND$(c)
  4.     'do whatever you need with this parameter
  6.  
Title: Re: GetCommandLine - winApi fn
Post by: Aurel on July 06, 2021, 06:11:08 am
thanks Felipe
so that is how work..cool and simple
if that work then there is no need for api calls
Title: Re: GetCommandLine - winApi fn
Post by: Aurel on July 06, 2021, 06:24:41 am
Yes
work as expected...
Title: Re: GetCommandLine - winApi fn
Post by: FellippeHeitor on July 06, 2021, 07:58:12 am
Command$(0) actually returns your own program name. User parameters start at index 1.
Title: Re: GetCommandLine - winApi fn
Post by: George McGinn on July 06, 2021, 09:12:31 am
Very similar to argv[0] in C/C++

Questions - 1) Is it only the program name if that name is available? In other words, if the host does not provide it, is it NULL?  2) And it "represents" the program name, not necessarily is the program name, is that also true (from the ISO C11 standard) or does QB64 use the compiled name, or the executable (If after I compile I decide to rename the binary)?

According to the C++ Standard, section 3.6.1 (See http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2014/n4296.pdf (http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2014/n4296.pdf)):
Quote
... argv[0] shall be the pointer to the initial character of a NTMBS that represents the name used to invoke the program or ""


Quote from: FellippeHeitor on July 06, 2021, 07:58:12 am
Command$(0) actually returns your own program name. User parameters start at index 1.
Title: Re: GetCommandLine - winApi fn
Post by: SpriggsySpriggs on July 06, 2021, 09:15:48 am
@George McGinn Command$(0) will be the full path that is resolved to the running executable. Give it a try.
Title: Re: GetCommandLine - winApi fn
Post by: Aurel on July 06, 2021, 09:22:09 am
Quote
Command$(0) actually returns your own program name.

Yes Felipe ..i want that
situation ..usage

text editor open file
with ShellExecute we call our program
which receive this file path and do execution/processing...etc
simple isn't ?
Title: Re: GetCommandLine - winApi fn
Post by: Aurel on July 06, 2021, 09:24:42 am
Quote
Command$(0) will be the full path that is resolved to the running executable

exactly... ;)


PS..stupid me i figured why my editor don't run .exe ..heh because of
directory name with . (dot) in 1.5 so i changes into 1_5 and voila !!!
Title: Re: GetCommandLine - winApi fn
Post by: George McGinn on July 06, 2021, 09:29:38 am
It will get the name of the executable, even the new name after renaming it.

So, unlike the mainframe compilers that put the compiled name in the binary (was used to check to make sure the right name was used to invoke it, part of security checking back then), this command must do a DIR type of command to fetch where and what the executable is.

Note: The security checking was to make sure that a renamed binary was not inserted into a production system. Yes, there were ways around it, and when CICS came about, more robust module integrity checks were put into place (some by me back then). Something similar can be done in QB64,


Thanks.

Quote from: SpriggsySpriggs on July 06, 2021, 09:15:48 am
@George McGinn Command$(0) will be the full path that is resolved to the running executable. Give it a try.
Title: Re: GetCommandLine - winApi fn
Post by: SpriggsySpriggs on July 06, 2021, 09:31:52 am
@George McGinn It's using argv and argc.... like any other C/C++ program would

Code: C++: [Select]
  1. func_command_count = argc;
  2. func_command_array = argv;
Title: Re: GetCommandLine - winApi fn
Post by: Aurel on July 06, 2021, 09:45:59 am
Quote
So, unlike the mainframe compilers that put the compiled name in the binary

WHAT ?...error message
Note:
any windows app build with native api compiled with C/C++ you can change name
Text Only | Text with Attachments