Iter
- Macro
- April 17, 2026
Table of Contents
Iter
IterDescription
Memory iterators are there to allow reading regions of memory by remembering current read position and the size limit. With proper checking we can guarantee that we can never overflow or underflow when reading a memory region This also means that Iter objects are created for use with only one reading operation, and one object in their lifetime. The designed API does not allow modifications to the data Iter is iterating over FIELDS: - data : Pointer to memory we’re iterating over - length : Number of objects in memory. - pos : Current iterating position. - size : Alignment requirements (if-any), must be at-least 1 - dir : Iteration direction, -1 or 1
Usage example (Cross-references)
- In
Iter.c:1:
#include <Misra/Std/Utility/Iter.h>
#include <Misra/Std/Log.h>
- In
Utility.h:16:
#define MISRA_STD_UILITY_H
#include <Misra/Std/Utility/Iter.h>
#include <Misra/Std/Utility/Pair.h>
#include <Misra/Std/Utility/StrIter.h>
- In
Access.h:7:
#define MISRA_STD_CONTAINER_VEC_ACCESS_H
#include <Misra/Std/Utility/Iter.h>
#include "Type.h"
- In
Type.h:12:
#include <string.h>
#include <Misra/Std/Container/Vec/Type.h>
#include <Misra/Std/Utility/Iter/Type.h>
#include <Misra/Types.h>
- In
StrIter.h:5:
#include <Misra/Std/Container/Vec/Type.h>
#include <Misra/Std/Utility/Iter.h>
#include <Misra/Types.h>
- In
StrIter.h:8:
#include <Misra/Types.h>
typedef Iter(char) StrIter;
typedef Vec(StrIter) StrIters;
- In
Iter.h:11:
// clang-format off
#include "Iter/Type.h"
#include "Iter/Init.h"
#include "Iter/Access.h"
- In
Iter.h:12:
// clang-format off
#include "Iter/Type.h"
#include "Iter/Init.h"
#include "Iter/Access.h"
#include "Iter/Move.h"
- In
Iter.h:13:
#include "Iter/Type.h"
#include "Iter/Init.h"
#include "Iter/Access.h"
#include "Iter/Move.h"
// clang-format on
- In
Iter.h:14:
#include "Iter/Init.h"
#include "Iter/Access.h"
#include "Iter/Move.h"
// clang-format on