technical request

[DarkBeam]

Jesse, when I open a function I see something like that
.Double paramname1=0
.Integer pn2=3

those are stored in edi+something in read only mode

I am sayin, what if we make a new field type, read write, not displayed in screen that stores additional data? example

!Double dimension1=0

allocates in edi+something read write space for an additional variable double, initially zero.

this would make possible more formulas pleaseeee

[DarkBeam]

Another solution, a [VARIABLES] section, similar to [CONSTANTS], data stored in ESI and so on (read write access )

[Jesse]

Already thought of this, but many changes have to be made because by now each calculation thread is sharing the formulas, so no writing is allowed - else you get artifacts of course.
I would have to program that each thread gets it own formula with variables.

A more general use of formulas is also on the todo list, but i guess this needs really some time until i get there...

[DarkBeam]

Okay understood thanks

[DarkBeam]

Another idea is a 'pre-calculation' code called just to calculate some constants that depend on the user data, but this is not so urgent
Another idea is a support for 2d angle matrix (plane rotation) - barely compute sine and cosine of the chosen angle. Not urgent but handy for sure

[cKleinhuis]

Another solution, a [VARIABLES] section, similar to [CONSTANTS], data stored in ESI and so on (read write access )

be sure n

Already thought of this, but many changes have to be made because by now each calculation thread is sharing the formulas, so no writing is allowed - else you get artifacts of course.
I would have to program that each thread gets it own formula with variables.

A more general use of formulas is also on the todo list, but i guess this needs really some time until i get there...

be sure not to trade speed against flexibility.... such modifications could radically slow down the program for a *rarely*(?) used feature!

[DarkBeam]

No, absolutely... Load a pack of bytes takes no time and it will be done only if necessary (example, phoenix fmla)

[Jesse]

be sure not to trade speed against flexibility.... such modifications could radically slow down the program for a *rarely*(?) used feature!

Of course i am always trying to not decrease speed or to have good reasons to loose some precents.

For the variables i have in mind to make an optional initialization code for formulas that will be performed before the iterations, so max 6 tests for zero pointer would be added on usual formulas, should not decrease speed that much.
For the more general formula combination with interpolation, alternation and DEcombination i had to test it before and would be only satisfied if speed decrease is under 10 percent.