Thanks, I didn't know.
I will update the documentation accordingly.
[edit]
Done:
- KeyPgVar → fxm ['STATIC' can be put in front of 'VAR' to define a static variable]
- KeyPgStatic → fxm ['STATIC' can be put in front of 'VAR' to define a static variable]
- KeyPgByrefVariables → fxm ['STATIC' can be put in front of 'VAR' to define a static variable]
- KeyPgShared → fxm ['STATIC' can be put in front of 'VAR' to define a static variable]
- ProPgVariableLifetime → fxm ['STATIC' can be put in front of 'VAR' to define a static variable]
- ProPgReferences → fxm ['STATIC' can be put in front of 'VAR' to define a static variable]
VAR as a topic
Re: VAR as a topic
Is there anyone who is against not using 'VAR' in examples for the last 4 documentation pages above (one would leave it for the first 6 documentation pages above, and also obviously for the VAR documentation page itself) ?fxm wrote:Except the 'VAR' documentation page, there are 10 other documentation pages using the 'VAR' keyword in their 'Example' paragraph:In my opinion, this is not at all justified for only the last 4 cases.
- - __FB_ARG_LEFTOF__
- __FB_ARG_RIGHTOF__
- __FB_UNQUOTE__
- BYREF (variables)
- Cairo
- Operator PROCPTR (Procedure pointer)
- Operator Step (Iteration)
- Properties
- STRING
- THREADDETACH
[edit] (04 Sep 2021)
Done now.