why can a variable declaration do this?

[charles]

i been playing with omikron and noticed a example code can adheare to this format ,, but only in omikron .... this is flexable but also udmbfounding ,, why would they permit such behaviour and would it be benificial?

here is an example
strg$=" "*256
print strg$

but then the string is only three "| " colons

or

local i$=" "*128

who knows what this does i freaked when the first example worked ,????

like is it multipling the orinigal word into a new string or does it repeat as many times as it's bound too?

omikron v.4 i believe

charles

[charles]

ignore this threaDd please , i got differnet results from version 3,.01 of omikron to version 4.0 of omikron...

version four will make a string of letters specified in S$
like S$="F"*4 will result in FFFF

but version 3 calculated like a math equation ,might be buggy ,

sorrry
charles

[lp]

s$=STRING$(4,"F");

Does the same, but works in all versions of GFA.

[charles]

lonny in your expert opinion why does gfa have these 2 options? just from different versions
of gfa carried through the years i suspect ?

#1
s$=space$(90)

or

#2
s$=string$(90," ")

same stuff , no?

charles

[lp]

You over look the obvious.
One is more common and thus easier to remember.
Also one is faster, since less parameters.