Sorry your browser is not supported!

or:



Of course, if I want to create 200+ individual turtles, it makes sense to make an array of turtle types. But is there anything won by creating a single game type?

On the above your type is still being made a global :p

The question then is type better than individual variables?

The answer of course is "it depends"

Types are organizational structures. If they help you organize, then they are better. If they create unneccessary complication, then maybe not. It really depends on the data used in any given situation

Will you ever need to pass all this data together into a function? If yes, then a type is the way to go as it'll be easier passing 1 variable rather keeping track of multiple parameters.

And this is me just nitpicking, but in your first example you write GAME in all caps. Generally speaking, constants are all capitalized. But it's up to you as it really makes no difference on the code other than general readability.

Thanks guys! I traced down the source which made me think about this: Page 546 in the AppGameKit official tutorial guide:



The argument for a global game type is that it is a smart way to make everything within it global.

And I can see that it is somehow more neat to have it all inside an overall type. Kind of like how I don't like placing file directly in the root of my external drives, but always creates folders. I guess this is mostly down to personal preferences.

Yet, it look like types can easily be saved/loaded to the harddrive using JSON:

https://www.appgamekit.com/documentation/guides/12_array_changes.htm

So ease of saving/loading could be a reason to put stuff into types, maybe.

Regarding UPPERCASE, I think it's great that BASIC is ignoring case. Other languages should copy this! Yet, I'm still unsure what use of case gives the best readability. BTW, Vintage BASIC code prefers to type everything except variables in uppercase.