FileOpen documentation $FO_BINARY

[mLipok]

FileOpen documentation  about $FO_BINARY  in Remark says:

Quote

A file can be read as binary (byte) data by using FileOpen() with the binary flag.

Tesiting in this way:
 

Local $hFile = FileOpen(@ScriptDir & "\test.pdf", $FO_READ + $FO_UTF8_NOBOM + $FO_BINARY)
Local $dFileContent = FileRead($hFile)
FileClose($hFile)

MsgBox(0, @ScriptLineNumber, VarGetType($dFileContent))

I get "Binary" in the MsgBox

Question:

A Binary variable in AutoIt is equivalent to what type of variable in C ++?
And what type in C# ?

I need this to be able to use the ActiveX library, which currently only supports data access in files and streams. For this reason, I talked to their DevTeam, but I need to know what type of data I can input as input and what I expect output.

Edited October 12, 2021 by mLipok

[TheDcoder]

24 minutes ago, mLipok said:

Tesiting in this way:

It's an error to combine both $FO_UTF8* and $FO_BINARY, use only one of them.

25 minutes ago, mLipok said:

A Binary variable in AutoIt is equivalent to what type of variable in C ++?

Since C++ is basically C with a lot of extra bells and whistles, it would be an array of `char` (char[]). The `char` type represents a single byte and with an array of them we can represent any binary value.

Sorry about the C# stuff, I have no idea as I have never used it. OOP languages tend to implement it as a buffer or stream class/object/thing. JS for example has ArrayBuffer.

[markyrocks]

Binary in c++ and c# is most commonly stored in a byte, byte[] or vector<byte>.  There's also a bitset class (c++) that makes individual bits more easily accessible.  Not sure if c# has something similar.  When you are talking about bytes in terms of reading and writing to files its very common to use a stream.   There's a variety of streams available with different options.  Edit: A stream can be a storage container the only difference is the way it behaves.

If you want to get down to the reality of the situation every piece of data is stored in Binary for every data type.  Depending on the type its given just associates different operator behavior to the data aswell as implicit conversions in something like a display output.  

 

Edit: sorry c# doesn't have vectors it would be a List<byte>

Edited October 12, 2021 by markyrocks

[Danyfirex]

It's Variant of safearray of bytes. in C++ is Variant with a safe array VT_ARRAY+VT_UI1. I C# When using COM It's automatically casted using byte[] , dynamic or object (Of course, it is possible that one of the three types of data mentioned may have an advantage over each other. I am not an expert on COM) objects.

Edited.

Saludos

Edited October 12, 2021 by Danyfirex
Edited

[mLipok]

Thanks so much.

[Danyfirex]

If You want to learn more about C++/AutoIt variables Check this nice explanation of @LarsJ

 

Saludos

[mLipok]

1 minute ago, Danyfirex said:

If You want to learn more about C++/AutoIt variables Check this nice explanation of @LarsJ

 

Do you want my head to explode?

 

[mLipok]

10 minutes ago, Danyfirex said:

It's Variant of safearray of bytes. in C++ is Variant with a safe array VT_ARRAY+VT_UI1. I C# When using COM It's automatically casted using byte[] or dynamic.

So if I understand well.... 
When using COM it is automatically converted/casted between this two data types in both ways. From COM to AutoIt and form AutoIt to COM, of course accordingly.

[Danyfirex]

8 minutes ago, mLipok said:

So if I understand well.... 
When using COM it is automatically converted/casted between this two data types in both ways. From COM to AutoIt and form AutoIt to COM, of course accordingly.

Yes Sir.

 

Saludos

[markyrocks]

Just for the record a variant is just a templated class wrapped around a storage container which is a void* allocated block of memory and the data just gets mem copied on the way in and cast on the way out.  There is more to it but it's not witchcraft.