Built-in way to get the standard handles?

[vefatica]

In particular, is there a built-in way to get the STD_INPUT_HANDLE?

 

[vefatica]

Never mind. This works.

v:\> echo %@fileopen[con:,r]
88

 

[Joe Caverly]

Why does the GetStdHandle API return a different result?

@setlocal
@echo off
set ConA=%@fileopen[con:,r]

set STD_OUTPUT_HANDLE=%@convert[16,10,FFFFFFF5???]
set STD_INPUT_HANDLE=%@convert[16,10,FFFFFFF6???]

echo STD_OUTPUT_HANDLE: %STD_OUTPUT_HANDLE
echo  STD_INPUT_HANDLE: %STD_INPUT_HANDLE

set ConAA=%@winapi[kernel32.dll,GetStdHandle,%STD_OUTPUT_HANDLE]

echo    Using @fileopen: %ConA
echo Using GetStdHandle: %ConAA
@endlocal

E:\Utils>GetStdHandle.btm 
STD_OUTPUT_HANDLE: 4294967285
 STD_INPUT_HANDLE: 4294967286
   Using @fileopen: 80
Using GetStdHandle: 84

Joe

 

[vefatica]

%@Fileopen[con:,r] is the input handle.

Your script asked for the output handle. With a small modification ...

v:\> grep winapi joe.btm
set ConAA=%@winapi[kernel32.dll,GetStdHandle,%STD_INPUT_HANDLE]

v:\> joe.btm
STD_OUTPUT_HANDLE: 4294967285
 STD_INPUT_HANDLE: 4294967286
   Using @fileopen: 88
Using GetStdHandle: 88

 

[Joe Caverly]

Glad it was something simple.

Thanks @vefatica

 

[vefatica]

set STD_OUTPUT_HANDLE=%@convert[16,10,FFFFFFF5???]

What are the question marks all about?

 

[Joe Caverly]

??? is a type-specifier in PowerBASIC,
which forces hexadecimal values to evaluate as unsigned.

In PowerBASIC, &HFFFFFFF6 is treated as a signed long-integer.

In PowerBASIC, &HFFFFFFF6??? is treated as an unsigned double-word.

Cut-and-Paste from the PowerBASIC WinBase.inc file;

::
:: %STD_INPUT_HANDLE  = &HFFFFFFF6???  '(DWORD)-10
:: %STD_OUTPUT_HANDLE = &HFFFFFFF5???  '(DWORD)-11
:: %STD_ERROR_HANDLE  = &HFFFFFFF4???  '(DWORD)-12
:

Forgot to remove them after pasting to my .btm.

Looks like @convert ignores them...

E:\Utils>echo %@convert[16,10,FFFFFFF6???]
4294967286

E:\Utils>echo %@convert[16,10,FFFFFFF6]
4294967286

Joe

 

[vefatica]

Yeah, I saw that. Apparently it just stops reading when it encounters a character not in [0-9a-zA-Z] and later chokes if a character isn't valid in the specified input base.

v:\> echo %@convert[16,10,F!FFFFFF5]
15

v:\> echo %@convert[15,10,F!FFFFFF5]
TCC: (Sys) The parameter is incorrect.
 "%@convert[15,10,F!FFFFFF5]"