| |
|
|
| yet get Arrays as Procedures-Parameter byRef instead of byVal transfer, means only The address instead of a copy. this is of course faster, can but To unexpected Ergebnissen lead in a slight To erlernenden Language.
now go Arrays as Procedures-Parameter standardmäßig byVal transfer, except one setting one @ to whom Variablennamen in the Parameterdeklarationsanweisung:
standard, byVal:
If byRef erwünscht (faster):
On Parameter, The not of type aray transfer go, has @ none Einfluss, however becomes The check for this Parameter on a aray-copy at settle the @-Zeichens shorted.
with functions, with them it on supreme speed ankommt, is means a optimization by @ for each Parameter with einzubeziehen.
deference:
an similar entrapment is simple allocate Array=Array:
var a b=[10 20 30]
a=b
a[0]=55
print b// shows 55,20,30 though b syntaktisch not manipulating watts
want is a copy of a aray for such Zuweisungen, then can for The function arr uses go:
|
|
|
| |
|
|
|
HofK | If @parameter in the Prozedurdefinition this Parameter as "At resse" -mistake in writing aware- commit, means The reference on the Parameter, ought to one my, that a=b for arrays too The copy of b to a bring and then a=@b The reference commit. so bräuchte one here no arr().
what speaks against it? what übersehe I thereby? |
|
|
| |
|
|