Guidelines for Contributing to QB64

[Richard]

Our guidelines are the same as always:


Quote from Galleon:

I was recently asked for guidelines about the process for contributing to QB64's source code/core functionality.

I am supportive of ANY change to QB64 which:
...
6) Does not allow mixed language/CPU specific command integration (such as inline C++ code, assembly, etc)
...

I disagree with point #6.

Assembly should be allowed in my opinion - some other BASICs have it.

My understanding is that QB64(pe) will only work on computers with INTEL based processors (putting aside Virtual Machine implementation, which I do not think many users of QB64 are heavily involved with).

So, although QB64 is cross-platform compatible - it will not work on a MAC that is non-Intel - so QB64 is processor (class) specific.

There are some commands. for instance, that cannot work on a MAC, and I suppose on LINUX - those commands I gather may use Windows API's.


I found it extremely difficult (but still possible) to have the "equivalent" of in-line Assembly in QB64 - though in my case, it was worth the trouble. 

The author of the quoted "rules" apparently, in the early days of development - actually used M$ PDS 7.1 to create the so-called QB 4.5 compatible package, known now as QB64(pe), that we use today - sounds a bit silly to me (PDS 7.1 has more features than QB 4.5).