xkernel a0ff8e413e add a check for the return of OBJ_new_nid() | 2 år sedan | |
---|---|---|
.. | ||
README.md | 4 år sedan | |
build.info | 8 år sedan | |
o_names.c | 2 år sedan | |
obj_compat.h | 2 år sedan | |
obj_dat.c | 2 år sedan | |
obj_dat.h | 2 år sedan | |
obj_dat.pl | 3 år sedan | |
obj_err.c | 3 år sedan | |
obj_lib.c | 4 år sedan | |
obj_local.h | 2 år sedan | |
obj_mac.num | 2 år sedan | |
obj_xref.c | 2 år sedan | |
obj_xref.h | 2 år sedan | |
obj_xref.txt | 3 år sedan | |
objects.pl | 3 år sedan | |
objects.txt | 2 år sedan | |
objxref.pl | 3 år sedan |
To cover all the naming hacks that were previously in objects.h
needed some
kind of hacks in objects.txt
.
The basic syntax for adding an object is as follows:
1 2 3 4 : shortName : Long Name
If Long Name contains only word characters and hyphen-minus
(0x2D) or full stop (0x2E) then Long Name is used as basis
for the base name in C. Otherwise, the shortName is used.
The base name (let's call it 'base') will then be used to
create the C macros SN_base, LN_base, NID_base and OBJ_base.
Note that if the base name contains spaces, dashes or periods,
those will be converted to underscore.
Then there are some extra commands:
!Alias foo 1 2 3 4
This just makes a name foo for an OID. The C macro
OBJ_foo will be created as a result.
!Cname foo
This makes sure that the name foo will be used as base name
in C.
!module foo
1 2 3 4 : shortName : Long Name
!global
The !module command was meant to define a kind of modularity.
What it does is to make sure the module name is prepended
to the base name. !global turns this off. This construction
is not recursive.
Lines starting with #
are treated as comments, as well as any line starting
with ! and not matching the commands above.