Associative arrays.

Follow-up to my post of 12/11/2015 11:23 PM: The desired effect can apparently be achieved by using CHR$(10) at the end of every line except the last one, then use CHR$(13), e.g. after KEY 5,"CLS"+CHR$(10)+"PRINT 55"+CHR$(13)

SORT on an array with zero elements gives an error. DIM Z$[0]:SORT Z$ Out of range(SORT:1)

The ability to load a specified part, not all, of a text file into a string variable.

Allow arrays of arrays.

A way for a DATA string value to include the 'quote' character CHR$(34).

A way to tell if the currently-running instance of a program was launched from the SMILE button or not.

Anything after CHR$(13) in a KEY string is ignored, e.g. after KEY 5,"CLS"+CHR$(13)+"PRINT 55"+CHR$(13), pressing key 5 will clear the screen but not print 55.

In Direct mode, RUN cannot be on the same line as another command, e.g. PROJECT "P":LOAD "L":RUN causes Syntax Error (RUN 0 at the end also gives Syntax Error).

I'm going to say it again: Documentation. It is not only a shame, it is disrespectful to your coding team. They have worked and tried to make things good and easy for BASIC programmers. Not to document their efforts is to devalue their work and also to disrespect the users.

Currently, LOAD and SAVE can only work inside the current project. Request: remove this restriction for both LOAD and SAVE. If that is too big, then, smaller request: remove this restriction for LOAD.

Documentation of all the features of the language. It is a shame there are things like the KEY() function, which someone took the trouble to code, but no-one can benefit from, except by accident.

Allow the use of the PROJECT command within a program. Even if that means a mandatory dialog.

X32KX4JP VAL("200") gives 200. VAL("200 dogs") gives 0. VAL("200 dollars") gives 200.

A guarantee that, at least when multiplayer starts, the 'terminal ID' numbers (MPRECV 'SID', MPSTAT, MPNAME$, MPGET), are 0 and 1 (when 2 consoles are in the initial connection), 0 1 and 2 (for 3 consoles), or 0 1 2 and 3 (for 4 consoles).

When one console performs two MPSETs, the effects will not be observed (with MPGET) on a second console in the opposite order.

Clear specification on when an MPRECV buffer overflow will occur - or, at least, a clear guarantee of how MPRECV may be used without causing an overflow, something like "The receive buffer is guaranteed not to overflow so long as the number of MPSENDs does not exceed 15 more than the number of successful MPRECVs".

Clear specification on when an MPSEND buffer overflow will occur - or, at least, a clear guarantee of how MPSEND may be used without causing an overflow, something like "MPSEND is guaranteed not to cause a send buffer overflow if it is used no more than 4 times in 5 frames".

There's nothing wrong with what you have done, but just so you know, there's no need for two commands READ C$ ARRAY$[I]=C$ ARRAY$[I] can be considered just another string variable, so it is more common to use READ ARRAY$[I]

For _*EVERY*_ circumstance in which an error may occur while running a program, ensure there is some way to programmatically check beforehand whether the error would occur - e.g. there is a way to check for 1D array index out of bounds, using LEN, but LOAD "DAT:DATFILE",DATARRAY will cause an error if DATARRAY has the wrong number of dimensions, and I cannot check this before getting the error.