Ronny Otto

Even shorter: ``` SuperStrict Framework BRL.StandardIO Function GetString:String() Print "GetString() called" Return "Test" End Function Print GetString()[0..] ``` ``` GetString() called GetString() called Test ```

the fix looks ... quite "cleaning up". Nice job.

```BlitzMax SuperStrict Framework brl.StandardIO Struct STest Field X:Int Field Y:Int Method SetX(value:Int) X = value End Method End Struct Local myArr:STest[5] myArr[0].SetX(10) Print myArr[0].X myArr[0].Y = 10 Print myArr[0].Y Local...

The index is maybe only useful in connection with `values()` (arrax) and `.length` Dunno what other benefits it could provide.

I did not check if "Values()" creates a new array each time..or returns a predefined one. So all the fuzz is more or less based on that code by scaremonger...

> > Also given: enums exist during compile time, so stuff can be done in that step already, compared to runtime-array-traveling. > > But does that matter? It would only...

Hmm ok ... so meanwhile it could `return myPrecalculatedArray[..]` - so a simple array copy instead of an array which it fills during runtime.

@Scaremonger By chatting with @davecamp I saw him using something which you could kinda use as ".length" alternative. He simply added a "LastID" at the end of the enum. ```Blitzmax...

as Values() creates a new array just to retrieve the length ... while "lastID" is populated on compile time. Regarding enum name - I just made up the example without...

Seems for `Type` it calls the overloaded new(value1,value2), while for `Struct` this does not happen: type: ```C void __m_untitled1_STest_New_i(struct _m_untitled1_STest_obj* o,BBINT bbt_value) { __m_untitled1_STest_New_ii((struct _m_untitled1_STest_obj*)o,bbt_value,bbt_value); o->clas = &_m_untitled1_STest; #line 9...