---

7.20.2.1 struct x1f4_lxline_type

typedef struct x1f4_lxline_type {
    struct x1f4_track_type textflat_set;
    struct {
	struct x1f4_eelookup_type *eelookup_data;
    } eelookup_set;
    struct {
	int type;
    } datalink_set;
    struct {
	int type;
    } linetype_set;
    struct x1f4_trans_type resource_set;
    struct {
	int (*call)(void *, struct x1f4_nodelink_type *),
	    (*fine)(void *, void *, struct x1f4_nodelink_type **,
		     struct x1f4_nodelink_type *),
	    (*miss)(void *, void *, struct x1f4_nodelink_type **,
		    struct x1f4_nodelink_type *);
	void *text;
    } missbail_set;
    struct {
	void *fine;
    } transfer_set;
    struct {
	unsigned miss;
	const struct x1f4_nodetype_type *nodetype_data;
    } datatype_set;
    struct x1f4_frame_type autolink_set;
    struct x1f4_trans_type codelink_set;
} x1f4_lxline_type;

The x1f4_lxline_type record lists the application concerns related to the record library objects generation.

The fields that are always interpreted by the record library constructor function are:

linetype_set

specifies the type id to use for the introduced ‘record’ type (some number conveniencing the application, greater than X1f4_E4_LAST) as:

See Symbolic Types.

type

the id

datatype_set

specifies the data types that are to be allowed for record item data types (and for which the record operating functions need be generated) as:

miss

the data types count

nodetype_data

the array of struct x1f4_nodetype_type record data type descriptions, miss long. The data type descriptions detail such data operations as copying and freeing along data type identification (data type name and data type id).

See struct x1f4_nodetype_type.

The array is not used outside the list library object construction, no references inside it are recorded, it may come out of existence once the library object construction completed.

The fields that are interpreted only if so requested are:

See Record Library Generation Flags.

datalink_set

specifies the type id to use for the referred ‘data’ type as:

type

the id

The type id will be used to construct functions (like the ‘rc_progress’ and ‘rc_regress’ functions) that refer byte array objects. If such functions are to be constructed the record library object must be introduced the byte data library object, before any (byte data related) constructed function gets executed.

codelink_set

specifies the library data memory allocator (allocates memory for the library object construction purposes only).

See struct x1f4_trans_type.

See Memory Allocator Construct.

resource_set

specifies the data memory allocator (allocates memory for the data created while executing programs).

See struct x1f4_trans_type.

See Memory Allocator Construct.

textflat_set

specifies the error reporter.

See struct x1f4_track_type.

See Error Reporter Construct.

autolink_set

specifies the temporaries allocator.

See struct x1f4_frame_type.

See Temporaries.

See Temporaries Allocator Construct.

Interpreted upon X1f4_LXLINE_AUTOLINK.

missbail_set

specifies the consolidated disposal manager as:

miss

the object registration method

fine

the non recursive object registration method

call

the object deregistration method

text

the consolidated disposal context

See Consolidated Disposal.

See Consolidated Disposal Manager Construct.

transfer_set

specifies a function type mapper to be used as:

fine

the mapper object

See Function Pointers.

See Function Pointer Type Alloter.

Uses include error formatting.

eelookup_set

specifies a name lookup context as:

eelookup_data

the data type name lookup context, used for both error reporting and data type name retrieval

See struct x1f4_eelookup_type.