coderJeff's Home Page


My FB Stuff

Extern links


FreeBASIC version and dialect comparison

I have constructed several tables that compare capabilities and compatibilities between QB4.5, QBasic, the FreeBASIC dialects (fb, fblite, deprecated, and qb) and various release versions of FreeBASIC. One day, I would like this information (or something like it) to go in the FreeBASIC manual, but at the momment I think it would be too much work to maintain it in the FreeBASIC wiki directly.

This information has been provided in the hopes that it may be useful.

DISCLAIMER : By viewing these tables you are assuming all responsibilities for their use. The providers of this information make no warranties of any kind and assume no liability, whatsoever.

Comparisons by Dialect

These tables compare QB4.5, QBasic, and the FreeBASIC dialects for a single version of the compiler.

v0.21.0b (SVN as of 2008.08.22)  Features   Keywords 
v0.20.0b (2008.08.10)  Features   Keywords 

Comparisons by Version (As of 2008.08.22)

These tables compare features and keywords between versions of FreeBASIC from v0.20.0b back to version v0.14b (v0.16.1 was not an actual release, but the Jul-2006 testing release). Previous versions did not support all the dialects or have only one dialect, so in several cases, the closest matching dialect has been used instead.

fb dialect  Features   Keywords 
fblite dialect  Features   Keywords 
qb dialect  Features   Keywords 
deprecated dialect  Features   Keywords 

About the Comparisons

All of the information relating to FreeBASIC is automatically generated using a database and automated testing procedures based on the Windows release versions of the FreeBASIC compiler. The QB and QB4.5 features have been manually set.

For each item (row) in the table, there is a record in a database that along with information about the feature or keyword contains a small basic test source. The test source is compiled, linked, or executed for each version of the compiler and each dialect supported and the result is stored in the database. Each test will result in either success (yes, the feature is supported) or failure (no, the feature is not supported).

The stored test results are then exported to static HTML pages and uploaded to this server.