fixed a bug which allowed some statements to end in tokens other than semicolons...

[xonotic/gmqcc.git] / doc / gmqcc.1

diff --git a/doc/gmqcc.1 b/doc/gmqcc.1
index c8398389d6074d3594f00f6b93762bb6896a1f77..940afd0fa04919ccd81054ec782ee0d7ae66d5c1 100644 (file)
--- a/doc/gmqcc.1
+++ b/doc/gmqcc.1
@@ -339,10 +339,12 @@ __COUNTER__
 __COUNTER_LAST__
 __RANDOM__
 __RANDOM_LAST__
+__DATE__
+__TIME__
 .fi
 .in
-Note that fteqcc also defines __FUNC__, __TIME__, __DATE__ and
-__NULL__, which are not yet implemented.
+Note that fteqcc also defines __NULL__ which is not implemented yet.
+(See -funtyped-nil about gmqcc's alternative to __NULL__).
 .TP
 .B -frelaxed-switch
 Allow switch cases to use non constant variables.
@@ -445,6 +447,14 @@ Adds a global named 'nil' which is of no type and can be assigned to
 anything. No typechecking will be performed on assignments. Assigning
 to it is forbidden, using it in any other kind of expression is also
 not allowed.
+.sp
+Note that this is different from fteqcc's __NULL__ in that gmqcc
+generates an actual empty global, rather than using the global at
+offset 0 because it would overlap with the global RETURN variable when
+dealing with vectors, which starts at offset 1. Setting a vector to
+__NULL__ in fteqcc causes only the vector's x component to be 0.
+However, its y and z components will contain the previous x and y
+components of the global OFS_RETURN.
 .TP
 .B -fpermissive
 Various effects, usually to weaken some conditions.