Readme states that AUTO_EVAL_STRINGS command:
If used, an EVALUATE_BUFFER is implied everywhere possible. In particular, you can now "forget" about using it in FUNCTIONs and arrays.
I've tried to use following tp2 test code:
BACKUP ~test/backup~
AUTHOR ~K4thos (swit)~
VERSION ~beta 0.1~
AUTO_EVAL_STRINGS
BEGIN ~test~
NO_LOG_RECORD
OUTER_SPRINT test1 ~VARNAME~
OUTER_SPRINT test2 ~LOCALS~
OUTER_SPRINT test3 ~7~
<<<<<<<< .../test.baf
IF
Global("%test1%","GLOBAL",0)
Global("dummy","%test2%",1)
Global("dummy","GLOBAL",%test3%)
THEN
RESPONSE #100
Continue()
END
>>>>>>>>
COMPILE ~.../test.baf~
For some reason the outcome script looks like this:
IF
Global("%test1%","GLOBAL",0)
Global("%test2%dummy","",1)
Global("dummy","GLOBAL",157479)
THEN
RESPONSE #100
Continue()
END
but all variables are evaluated correctly if I use either:
COMPILE EVAL ~.../test.baf~
or
COMPILE ~.../test.baf~ EVALUATE_BUFFER
Why is that? I though AUTO_EVAL_STRINGS command supposed to do exactly the same thing as EVAL? If no than the description probably needs some carification.