Skip to content

Commit 005db81

Browse files
committed
embed.fnc: Add 'const_expr' as an option for apidoc args
The next commit will want this
1 parent 565fcc0 commit 005db81

File tree

1 file changed

+11
-9
lines changed

1 file changed

+11
-9
lines changed

embed.fnc

Lines changed: 11 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -315,15 +315,17 @@
315315
: like 'int' or 'char', and 'cast' by perhaps 'struct foo'.
316316
:
317317
: The complete list of conventions is:
318-
: block the argument is a C brace-enclosed block
319-
: cast the argument names a type which the macro casts to
320-
: number the argument is a C numeric constant, like 3
321-
: SP the argument is the stack pointer, SP
322-
: "string" the argument is a literal C double-quoted string; what's important
323-
: here are the quotes; for clarity, you can say whatever you want
324-
: inside them
325-
: token the argument is a generic C preprocessor token, like abc
326-
: type the argument names a type
318+
: block the argument is a C brace-enclosed block
319+
: cast the argument names a type which the macro casts to
320+
: const_expr the argument is an expression whose result is known at compile
321+
: time
322+
: number the argument is a C numeric constant, like 3
323+
: SP the argument is the stack pointer, SP
324+
: "string" the argument is a literal C double-quoted string; what's important
325+
: here are the quotes; for clarity, you can say whatever you want
326+
: inside them
327+
: token the argument is a generic C preprocessor token, like abc
328+
: type the argument names a type
327329
:
328330
: Unlike other arguments, none of these is of the form 'int name'. There is no
329331
: 'name'.

0 commit comments

Comments
 (0)