Re: Scoping of variables in block constructs

[Achim G. <Str...@ne...>]

sfeam via gnuplot-beta writes:
> Too complicated for me to work through in detail but one line
> is waving a red flag.   This line
>      set ytics @ticdef
> is almost certainly not what you want to do.

Ah, OK.

> The macro expansion operator @ is like a #define statement in C.
> It causes a substitution at the time the file/block/clause/program unit
> is read in.  It is _not_ reevaluated at run time.

I still can't quite figure out the consitions under which this was and
wasn't working for my example in various stages of its development, but
I think that must be the right explanation.

> An example of evaluation at run time would be:
>
>    ... loop that constructs ticdef ...
>    eval "set ytics " . ticdef

This seems all unnecessarily involved, so maybe I should rather ask if
there's a way to build up an explicit tics list piece by piece rather
than having to feed everyting as one single giant string?

Also, why is there no block "else if" or maybe even "elsif"?


Regards,
Achim.
-- 
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+

Wavetables for the Terratec KOMPLEXER:
http://Synth.Stromeko.net/Downloads.html#KomplexerWaves