Tabs, Error handling and Dimensions

[hap2u]

I like the tabs, an X will be included so they can be closed by mouse?

Dimensions still do not work?  I get an error when I run your example.
So for now I will have to use my work around.  If adding dimensions is messing things up perhaps a TRD(X,Y) command could be used to generate a third, fourth dimension. It is important that TRD(0,0) to TRD(limit,limit) generate a 1.2.3.4.....100.101 to limit integer. 
eg. MyArray(1,TRD(2,TRD(3,4))).  This would make it so programmer does not have to create two dims for each DIM(1,2,3).

Error handling seems to work well.  But strongly suggest you find a way for the user to generate an error.
This can be done with a command which activates Err, such as Ern=11 will generate an Err 11 error.
A group of numbers say 100-200 could be reserved for programmer generated errors.

Not  a great issue as it can be worked around with TRY1Start on error goto Try1catch1, etc; consider creating a TRY/CATCH/FINAL/END TRY command set to handle errors generated by the OPEN command and other commands with possible 'not found' alternate actions.

Command bloat and I are not buddies, hopefully the commands stay under 150, I love being able to use created variables such as Global$.
   




 

[Carl Gundel]

Apr 12, 2020 10:02:48 GMT -5 hap2u said:

I like the tabs, an X will be included so they can be closed by mouse?

Probably.  Not at the top of my list.

Dimensions still do not work?  I get an error when I run your example.
So for now I will have to use my work around.  If adding dimensions is messing things up perhaps a TRD(X,Y) command could be used to generate a third, fourth dimension. It is important that TRD(0,0) to TRD(limit,limit) generate a 1.2.3.4.....100.101 to limit integer. 
eg. MyArray(1,TRD(2,TRD(3,4))).  This would make it so programmer does not have to create two dims for each DIM(1,2,3).

Not sure I understand.  The following code does not work?

 dim myArray(5, 5, 5)
 for x = 0 to 5
   for y = 0 to 5
     for z = 0 to 5
       myArray(x, y, z) = x*y*z
       print myArray(x, y, z)
     next z
   next y
 next x

Error handling seems to work well.  But strongly suggest you find a way for the user to generate an error.
This can be done with a command which activates Err, such as Ern=11 will generate an Err 11 error.
A group of numbers say 100-200 could be reserved for programmer generated errors.

Interesting suggestion.

Not  a great issue as it can be worked around with TRY1Start on error goto Try1catch1, etc; consider creating a TRY/CATCH/FINAL/END TRY command set to handle errors generated by the OPEN command and other commands with possible 'not found' alternate actions.

Not for v5.0, sorry.  You say you don't like command bloat. 

Command bloat and I are not buddies, hopefully the commands stay under 150, I love being able to use created variables such as Global$.   

What do you mean by created variables, such as Global$?  More examples?