• CS_ERROR_SDG_NOT_PRESENT if no project is loaded,
• CS_ERROR_UNKNOWN_ABS_LOC_KIND if abs_loc kind is unknown,
• CS_SUCCESS otherwise.

• CS_ERROR_INVALID_ABS_LOC_KIND if kind is not valid,
• CS_SUCCESS otherwise.

• CS_ERROR_INVALID_ARGUMENT if abs_loc has kind cs_abs_loc_kind_function,
• CS_SUCCESS otherwise.

• CS_ERROR_INVALID_ARGUMENT if abs_loc does not have kind cs_abs_loc_kind_function,
• CS_SUCCESS otherwise.

• CS_TRUNCATED if out_string is not large enough to hold the entire variable name of abs_loc (and so the name was truncated),
• CS_SUCCESS otherwise.

Call this function with out_string NULL and capacity_bytes 0 (zero) to determine the memory needed to hold the name of abs_loc.

• CS_ABS_LOC_NOT_FUNCTION if abs_loc does not represent a function,
• CS_ERROR_SDG_NOT_PRESENT if no project is loaded,
• CS_SUCCESS otherwise

• CS_NO_REPRESENTED_STRING if abs_loc does not have a string representation,
• CS_TRUNCATED if out_string is not large enough to hold the entire string (and so the string was truncated),
• CS_SUCCESS otherwise.

Call this function with out_string NULL and capacity_bytes 0 (zero) to determine the memory needed to hold the representation of abs_loc.

• CS_ABS_LOC_HAS_NO_PDG if abs_loc is not local or local-static,
• CS_SUCCESS otherwise.

• CS_ABS_LOC_IS_GLOBAL if abs_loc represents a global,
• CS_SUCCESS otherwise.

• CS_ELEMENT_NOT_PRESENT if no AST of ast_family is associated with abs_loc.
• CS_ERROR_INVALID_ARGUMENT ast_family is not a valid cs_ast_family.
• CS_SUCCESS otherwise.

• CS_ELEMENT_NOT_PRESENT if no type cs_ast with family ast_family is associated with abs_loc.
• CS_SUCCESS otherwise.

• CS_NO_POSITION if no declaration vertex can be located,
• CS_SUCCESS otherwise.

• CS_ELEMENT_NOT_PRESENT if no declaration can be located,
• CS_SUCCESS otherwise.

• CS_ERROR_SDG_NOT_PRESENT if no project is loaded,
• CS_OUT_OF_ELEMENTS if there are no cs_abs_loc objects in the project,
• CS_SUCCESS otherwise.

• CS_OUT_OF_ELEMENTS if the iteration is complete,
• CS_SUCCESS otherwise.

• CS_SUCCESS if $param_num exists,
• CS_ELEMENT_NOT_PRESENT otherwise.

• CS_ERROR_SDG_NOT_PRESENT if no project is loaded,
• CS_ELEMENT_NOT_PRESENT if there is no cs_abs_loc associated with aname,
• CS_SUCCESS otherwise.

• CS_ERROR_SDG_NOT_PRESENT if no project is loaded,
• CS_ELEMENT_NOT_PRESENT if no such cs_abs_loc exists,
• CS_SUCCESS otherwise.

• CS_ERROR_SDG_NOT_PRESENT if no project is loaded,
• CS_ELEMENT_NOT_PRESENT if no such cs_abs_loc exists,
• CS_SUCCESS otherwise.

• CS_ERROR_INVALID_ARGUMENT if the cs_abs_loc_kind of abs_loc is not cs_abs_loc_kind_intermediate (expression temporary) or cs_abs_loc_kind_result (actual-out argument).
• CS_ELEMENT_NOT_PRESENT if a pretty-printed version of the AST is not available.
• CS_TRUNCATED if buf is not large enough to hold the entire pretty-printed AST (and so the string was truncated).
• CS_SUCCESS otherwise.

Call this function with buf NULL and capacity_bytes 0 (zero) to determine the memory needed to hold the entire pretty-printed AST for abs_loc.

This function entails less user overhead than cs_abs_loc_name(), and so can be more convenient to use; the tradeoff is that the returned value is not under user control and has a constrained lifetime.

This function differs from cs_abs_loc_string() in only one respect: the returned name will never have a -i suffix (for integer i).

This function entails less user overhead than cs_abs_loc_temp_source(), and so can be more convenient to use; the tradeoff is that the returned value is not under user control and has a constrained lifetime.

This function entails less user overhead than cs_abs_loc_represented_string(), and so can be more convenient to use; the tradeoff is that the returned value is not under user control and has a constrained lifetime.

• N<0 if aloc_a considered less than aloc_b
• N==0 if aloc_a and aloc_b are the same cs_abs_loc
• N>0 if aloc_a considered greater than aloc_b

The comparison is stable in the following sense. Suppose there are two analyses A1 and A2 generated with exactly the same inputs (including identical analyzed code, underlying build commands and ordering, command line and configuration settings, increment order and contents). Let a1 and b1 be two cs_abs_loc values in A1, and a2 and b2 be the cs_abs_loc values in A2 that correspond to a1 and b2 respectively. Then cs_abs_loc_stable_compare(a1,b1)==cs_abs_loc_stable_compare(a2,b2).

If you do not need comparison results to be stable across different analyses, use cs_abs_loc_compare(): it has better performance.

If you do not need hash values to be stable across analyses, use cs_abs_loc_hash(): it has better performance.

• CS_SUCCESS on success,
• CS_TRUNCATED if the provided buffer is not large enough to hold the handle.

• CS_SUCCESS on success,
• CS_ERROR_INVALID_ARGUMENT if abs_loc_handle is not valid,
• CS_ERROR_IO_READ_PAST_EOF if the handle parameter is too short to be a valid handle.
• CS_ERROR_SDG_NOT_PRESENT if there is no current System Dependence Graph.
• CS_ELEMENT_NOT_PRESENT if the search for the pdg containing this abs_loc fails.

• N<0 if aloc_a considered less than aloc_b
• N==0 if aloc_a considered equal to aloc_b
• N>0 if aloc_a considered greater than aloc_b

For fixed cs_abs_loc values a and b in a single analysis, cs_abs_loc_compare(a,b) will always return the same value. However, cs_abs_loc_compare() will not necessarily return this same value when called on the corresponding cs_abs_loc values a' and b' in a different analysis. Function cs_abs_loc_stable_compare() provides some degree of stability across analyses, although restrictions still apply. If you do not need comparison results to be stable across different analyses, use cs_abs_loc_compare(): it has better performance.