Exploring BASIC Dialects via the "BASIC Data Types Explorer"

I've been particularly interested in the various data types across BASIC dialects.  Although interested in the data types themselves (including the related keywords and "sigils"), I've been particularly interested in how to enter that information and how to view that information.

Keep in mind that I'm no fan of "big requirements/analysis/design"   up front.  I much prefer an iterative/incremental (or evolutionary, or organic?) process.  Start prototyping/building something right out of the gate with what is known, and adjust as the magic of elucidation happens (i.e. all of the intertwingled bits and pieces become clear.)

I am no fan of sticks in my wheels and wheels stuck in the mud.  When I don't know how to handle something (name it, enter it, display it, etc.), I either go with either "just good enough" or "get back to it later."

Although I've got a pretty good sample database put together, I know I've skipped some data types for some BASIC dialects when I did not know how to handle the data types at that moment  (Meh: get back to them later.)

I've also picked dialects for which the data types were easy enough to find and understand.

Should you be interested in contributing, please see "How can you help?"

Please check out the (work-in-progress, i.e. subject to all kinds of change) BASIC Data Types Explorer.  

Links to click on (and open popup dialogs) look like this (light-blue rounded border and very light-gray background):

Cheers !

Some screenshots:

WIP: A Test "Sandbox" for the "Data Types" Editing Interface

Testing/playing with this "sandbox" window will not impact anything. 

WIP: Data entry setup for BASIC dialect data types (keywords and sigils)

The goal: the ability to identify for any BASIC dialect the data types supported by that dialect.  For each general/universal description of a data-type:

• we'll have a drop-down list of available keywords to choose from to identify the keyword used by the BASIC dialect to declare the related data-type for any identifier
• we'll have a drop-down list of available "sigils" ( one or more characters appended to an identifier, for indicating the identifier's data-type)
• for each list, we'll have a button for adding a new keyword/sigil applicable to the BASIC dialect being edited
• each list will be populated with the keywords/sigils previously entered for any BASIC dialect
• each list will also have the option "None" or "Not Supported" to indicate the dialect does not have a keyword and/or sigil for that data-type
• If a dialect has neither a keyword nor a sigil, then that data-type is not supported at all
• each list will also have the option "Unknown"

Just looking at the various string types for three BASIC dialects (QB64, FreeBASIC, and PowerBASIC, it is easy to see how things will be big/complex:

Click here to see the latest version of the "Charlie's About BASIC" TiddlyWiki.

To discuss, please use what you prefer:

• use the comments section in this blog
• join and use this Google Group
• or comment wherever I have shared a link to this blog entry