From: Rudolf Polzer Date: Sat, 7 May 2011 20:46:39 +0000 (+0200) Subject: make autocvar spec more clear X-Git-Tag: xonotic-v0.5.0~263^2~20 X-Git-Url: https://git.rm.cloudns.org/?a=commitdiff_plain;h=c12997229cf4d5429041096c70aa8f7647cdd431;p=xonotic%2Fxonotic-data.pk3dir.git make autocvar spec more clear --- diff --git a/qcsrc/server/extensions.qh b/qcsrc/server/extensions.qh index 4c15a46a4..e8f0236b2 100644 --- a/qcsrc/server/extensions.qh +++ b/qcsrc/server/extensions.qh @@ -591,11 +591,11 @@ float(float a) tan = #475; // returns tangent value (which is simply sin(a)/cos( //NOTE: copying a string-typed autocvar to another variable/field, and then //changing the cvar or returning from progs is UNDEFINED. Writing to autocvar //globals is UNDEFINED. Accessing autocvar globals after cvar_set()ing that -//cvar is IMPLEMENTATION DEFINED (an implementation may either yield the -//previous, or the current, value). Whether autocvar globals, after restoring -//a savegame, have the cvar's current value, or the original value at time of -//saving, is UNDEFINED. Restoring a savegame however must not restore the -//cvar values themselves. +//cvar in the same frame is IMPLEMENTATION DEFINED (an implementation may +//either yield the previous, or the current, value). Whether autocvar globals, +//after restoring a savegame, have the cvar's current value, or the original +//value at time of saving, is UNDEFINED. Restoring a savegame however must not +//restore the cvar values themselves. //In case the cvar does NOT exist, then it is automatically created with the //value of the autocvar initializer, if given. This is possible with e.g. //frikqcc and fteqcc the following way: