Hi José,

Not big deal...
The SECURITY_DESCRIPTOR_CONTROL macro is absent...
Like in PB, WinNT.inc : MACRO SECURITY_DESCRIPTOR_CONTROL=WORD

C / C++ is the way to go... The Drakes are a big disappointment imo. I wonder wether they put any effort in a new pb compiler. But even if, too many years have passed since the last version and I wonder the PB will be able to attrack new customers.

And for hobbyist: Delphi, CBuilder and Visual C, C# are free. There are enough options.

The enterprise I am working switched to Delphi. We never regretted it.

Lets face it: BASIC is dead.

Quote from: Anthon Com on December 05, 2019, 12:37:50 AM
Look at Freebasic,  which is already dead and so is QuickBasic64  and those other old basic languages are either dead or dying.

please don't state your opinion as a matter of fact, FreeBasic is actively being developed

For SDK programmers the learning curve is not that long, tooks me 6 monthes to translate my GDImage DLL to plain C/C++.

But for DDTer's that is another problem and i understand the concern.

Anyway i will always prefer a compiler based on a pool of programmers rather than one based on the work of a few.

Bob Zale syndrome is difficult to gauge, what we need is a compiler urgently that can do the work for the time being, something
that can translate Powerbasic programs directly, without the steep learning curve such as C++ programming language

Look at Freebasic,  which is already dead and so is QuickBasic64  and those other old basic languages are either dead or dying.
We can't afford the time to convert to other languages as business is an ongoing concern.

We can't wait for Drake to put up another compiler for 64bits -- looks like NEVER. Since Drake isn't listening to its own customers
so Pluribasic and OxygenBasic  are the only answer now.

For a buisiness work, a compiler { that is a strategic choice }, must be not only rock solid, but offer a real guarantee that it will be maintained in the long range, to avoid the single man Zale's syndrom.

Hobbyist, of course, do what ever you want 

Pluribasic and OxygenBasic is the way to go 64bit and you can forget about the 32bit Powerless Basic

Yup Brian you are correct

      In 64bit O2,  handles and pointers must be converted to sys

        PB handles  conversion to  O2           
        DWORD  -->  sys
        LONG      -->  sys

        sys  is mainly  applicable to window handles and pointers, while all other variables remain unchange

     

In Oxygen it is called sys. In 32bit mode it is 4 byte, in 64bit mode it is 8.

sys hAddress

In PluriBASIC (oxygen based) it is called handle.

LOCAL hAddress AS HANDLE

WinDev uses the SYSTEM INTEGER (short SYSTEM)

automatically adapts to the size supported by the compilation mode (4 bytes for a program compiled in 32 bits, 8 bytes for a program compiled in 64 bits).

Example:

i is system int