mirror/tracy
1
0
Fork 0
mirror of https://github.com/wolfpld/tracy.git synced 2024-11-10 10:41:50 +00:00
Code Issues Packages Projects Releases Wiki Activity

Mention pseudo-dynamic string management.

Browse Source
This commit is contained in:
Bartosz Taudul 2020-10-12 00:09:39 +02:00
parent 7e4f857784
commit 6a443bcd48
1 changed files with 12 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

13
manual/tracy.tex
View File

@ -799,7 +799,18 @@ FrameMarkStart(sl_AudioProcessing);
FrameMarkEnd(sl_AudioProcessing); FrameMarkEnd(sl_AudioProcessing);
\end{lstlisting} \end{lstlisting}
Proper support for non-unique same-content string literals will be implemented in future. In some cases you may want to have semi-dynamic strings, for example you may want to enumerate workers, but don't know how many will be used. This can be handled by allocating a never-freed \texttt{char} buffer, which can be then propagated where it's needed. For example:
\begin{lstlisting}
char* workerId = new char[16];
snprintf(workerId, 16, "Worker %i", id);
...
FrameMarkStart(workerId);
\end{lstlisting}
You have to make sure it's initialized only once, before passing it to any Tracy API, that it is not overwritten by new data, etc. In the end this is just a pointer to character-string data, and it doesn't matter if it was loaded from program image, or if it was allocated on the heap.
Proper support for non-unique same-content string literals may be implemented in future.
\subsection{Specifying colors} \subsection{Specifying colors}