END OF AN ERA, FRACTALFORUMS.COM IS CONTINUED ON FRACTALFORUMS.ORG

so, can you be more specific about your array !?
is it different for different needs, is it created "on the fly"?
depending on what you do, various approaches might fit,
i am not perfect at coding uf, bot most of the stuff works somehow,
and the class system in general is just perfect for different formulas
and recombining them

so, if all classes shall have access to the same array, hmm, a memory
consumption approach would be to instanciate a class defining the array
in each of the classes ...

one approach to propagate the data to sub-property-classes might be
to define a base class for distributing an array to work with, and
the accessing functions for the array in the same base class
so that you could choose the array in a "root" formula, and in the
init part of your function you propagate the data to the lower classes
something like this:

in a base function
var theArrayClass
setData(arrayclass)
getDataFromArray(anydimensionalindex)

and then in the root class you let the user define the
array to work with, and in the init class you
call the setData function, which then propagates
the array to sub classes

clearly, any class using arrays should define the sub-classes
in an array like manner as well for accessing possible sub classes
to propagate the array to

First of all note that pi is accessed as #pi (to working resolution even if arbitrary) and so is exp(1) as #e - also using #pi/360.0 or similar in the code will pre-calculate at compile time.

As for writing formulas/colourings etc:

Rule 1: If you don't really need class-based formulas *use the old style* - class-based formulas are more generic and therefore *considerably* slower to execute because of the overheads required.

In the old style to do what you require simply add:

global:
  static float f[5]
  f[0]=1
  f[1]=2
  f[2]=3
  f[3]=4
  f[4]=5 ; or whatever constants are required

Before the init: section and in the code simply return a constant index i as f[ i ]

If you wish to use this in class-based formulas/colourings then the best way is have your own derived main formula base class and/or derived colouring formula base classes for divergent/convergent/both - simply put the code from the global section above in your derived base's init section - but with "static float f[5]" in the base's global variables section (protected/public etc.as you wish).