darkplaces/gmqcc
0
0
Fork 0
mirror of https://github.com/DarkPlacesEngine/gmqcc.git synced 2025-01-31 03:50:36 +00:00
Code Issues Projects Releases Packages Wiki Activity

manpage: A note about __NULL__ vs nil

Browse source
This commit is contained in:
Wolfgang Bumiller 2013-01-09 21:54:36 +01:00
parent d0efaa50d4
commit 06101d48e4
1 changed files with 9 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

9
doc/gmqcc.1
View file

@ -344,6 +344,7 @@ __TIME__
.fi .fi
.in .in
Note that fteqcc also defines __NULL__ which is not implemented yet. Note that fteqcc also defines __NULL__ which is not implemented yet.
(See -funtyped-nil about gmqcc's alternative to __NULL__).
.TP .TP
.B -frelaxed-switch .B -frelaxed-switch
Allow switch cases to use non constant variables. Allow switch cases to use non constant variables.
@ -446,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 anything. No typechecking will be performed on assignments. Assigning
to it is forbidden, using it in any other kind of expression is also to it is forbidden, using it in any other kind of expression is also
not allowed. 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 .TP
.B -fpermissive .B -fpermissive
Various effects, usually to weaken some conditions. Various effects, usually to weaken some conditions.