Hi
@FellippeHeitor Yes it is known that the lowlevel calling (CALL ABSOLUTE/ CALL INTERRUPT/ CALL INTERRUPTX) used also in theBob's code aren't supported by QB64 but it is emulated only the INT33 for the 3 first services.
Moreover other low level work is emulated and deprecated to use in code (INP, OUT, PEEK, POKE, DEF SEG, VARPTR, VARPTR$, SADD). Analog discussion about IOCTL and IOCTL$.
That is a choice of Galleon and of the QB64 developers team!The policy about the lowlevel work is forbidden in QB64 using the old ways.
Old ways that exhume 8-16 bit worlds are out!
But how can the QB64 coder access to the low level? The actual answer of QB64 developers team is
1. QB64 is not a language to make low level work like build a driver, work on wire, access to port but if you need to do some work surely there is anywhere a library (often DLL or C/C++ library) that you can integrate into your work.
2. for efficient memory access it has been added _MEM
(... please all you that know more to add others ways available today.)
So is the request to open to ASM inline and C inline in the other thread simply an attempt to have more control of machine towards low level coding ? Or also to implement some feature that is not developed into QB64 language and it is hard that QB64 developers team can support at time?
We can think that this kind of need is for expert programmers that must build something with QB64 but are valid C/C++ coders. In this case is better to open to ASM and/or C/C++ inline or a more robust support of integration of external library made by the expert coder?
The third way is that defined by Galleon in that old post
My new philosophy is to let QB64 be what the community want it to be. Even if we end up with 1000s of commands that barely get used by the majority, it is better than QB64 not being used at all. And if someone implements something incredibly stupid/unnecessary (such as a _HELLOWORLD command) the beauty of a repository is that it can always be rolled back later. Because of this philosophy, you won't see me standing in the way of any changes.
but this third way brings to QB64 developers team a pletora of work more than that they already had.