TT_PATTERN_PRINT(3)

πŸ“¦
version 2.5.3 Β· 2 versions
, in nixos 26.05

πŸ¦‹ tt_pattern_print(3) β€” format a pattern πŸ¦‹

okay so this is the tt_pattern_print(library call) page β€” manual-name vibes folded in right here, bestie β€” and it's all about tt_pattern_print(3). Let's get into it πŸ’…


πŸŽ€ NAME πŸŽ€

tt_pattern_print β€” format a pattern


✨ SYNOPSIS ✨

#include &<Tt/tt_c.h>
char *tt_pattern_print(
Tt_pattern *p);

πŸ’– DESCRIPTION πŸ’–

The tt_pattern_print function formats a pattern in the same way a message is formatted for the ttsession(1) trace and returns a string containing it. It's giving "make this pattern readable" energy, fr fr.

The p argument is the pattern to be formatted. That's the whole vibe check for the input.


🌈 RETURN VALUE 🌈

Upon successful completion, the tt_pattern_print function returns the formatted string. The application can use tt_ptr_error(3) to extract one of the following Tt_status values from the returned pointer:

  • TT_OK β€” The operation completed successfully. Slay.
  • TT_ERR_NOMEM β€” There is insufficient memory available to perform the function.
  • TT_ERR_POINTER β€” The pointer passed does not point to an object of the correct type for this operation.

🫢 APPLICATION USAGE 🫢

The tt_pattern_print function allows an application writer to dump out patterns for debugging. Lowkey iconic for when you need to peek at what's going on πŸ‘€


πŸ‘‘ SEE ALSO πŸ‘‘

Tt/tt_c.h - Tttt_c(5), tt_ptr_error(3).


footer check, bestie: the original footer is just tt_pattern_print(library call) β€” no extra source/version/date line was hiding there, so we're literally not inventing one. Byeee, go format those patterns πŸ’…πŸ’–

πŸ“¦ where this page comes from