What’s the Best Way to Store Data as Bytes and Separate Different Variables?

For what you’re trying to achieve, using tags or length indicators can make things easier. Instead of looking for delimiters, you could use a structure where you start with the length, then the tag, followed by the data itself. This organization lets you read the length first before diving into the data.

What you’re talking about is related to serialization. A straightforward approach for your array would be to first write down its length (which uses a fixed number of bytes), followed by the actual elements right after it. This gives you a clear start and end point when reading them back.

It’s worth noting that while you can create your own format, keeping it readable and maintainable is key—especially for anyone who might work on it later. Consider the long-term impact on your code readability and stick to conventions that make sense for quick comprehension afterwards.

You could start your array with the first byte representing the length of the array. This method is actually similar to what Pascal does with strings. It allows you to know how many elements to expect right from the outset.

You know, a lot of data files like .dat or .json handle these things for you. There’s no harm in experimenting with your own format—you’ll definitely learn how these structures work. Just remember that all files are ultimately a sequence of bytes, and that includes text files. If you choose to store data in a text file, consider setting up a clear format where each variable appears on a separate line; this way, it's easier to read each piece.