PCRE_CONFIG(3)

🎀 PCRE_CONFIG(3) — girl, let's talk about your regex library ✨

okay so bestie, this one's from the Library Functions Manual 💖 (that's the manual name, we're keeping it, it's part of the lore). It's all about PCRE — Perl-compatible regular expressions, no cap 🦋

🌸 NAME 🌸

PCRE — Perl-compatible regular expressions 💅

✨ SYNOPSIS ✨

#include <pcre.h>

int pcre_config(int what, void *where);

int pcre16_config(int what, void *where);

int pcre32_config(int what, void *where);

like, three whole flavors of the same vibe 🫶

💖 DESCRIPTION 💖

So this function? It's literally your little spy 🕵️♀️✨ It lets a client program find out which optional features are available in the version of the PCRE library it's using. Iconic behaviour, honestly.

The arguments are giving:

• what — a code specifying what information is required 👀
• where — points to where to put the data 📍

⚠️ okay so pay attention here bestie: the where argument must point to an integer variable — EXCEPT for PCRE_CONFIG_MATCH_LIMIT, PCRE_CONFIG_MATCH_LIMIT_RECURSION, and PCRE_CONFIG_PARENS_LIMIT, where it must point to an unsigned long integer, and for PCRE_CONFIG_JITTARGET, where it must point to a const char*. Don't get this wrong or it's giving chaos 😭

The available codes are:

• PCRE_CONFIG_JIT — availability of just-in-time compiler support (1=yes 0=no) 🔥
• PCRE_CONFIG_JITTARGET — string containing information about the target architecture for the JIT compiler, or NULL if there is no JIT support
• PCRE_CONFIG_LINK_SIZE — internal link size: 2, 3, or 4
• PCRE_CONFIG_PARENS_LIMIT — parentheses nesting limit
• PCRE_CONFIG_MATCH_LIMIT — internal resource limit
• PCRE_CONFIG_MATCH_LIMIT_RECURSION — internal recursion depth limit
• PCRE_CONFIG_NEWLINE — value of the default newline sequence:
  • 13 (0x000d) for CR
  • 10 (0x000a) for LF
  • 3338 (0x0d0a) for CRLF
  • -2 for ANYCRLF
  • -1 for ANY
• PCRE_CONFIG_BSR — indicates what \R matches by default:
  • 0 — all Unicode line endings
  • 1 — CR, LF, or CRLF only
• PCRE_CONFIG_POSIX_MALLOC_THRESHOLD — threshold of return slots, above which malloc() is used by the POSIX API
• PCRE_CONFIG_STACKRECURSE — recursion implementation (1=stack 0=heap)
• PCRE_CONFIG_UTF16 — availability of UTF-16 support (1=yes 0=no); option for pcre16_config() ⭐
• PCRE_CONFIG_UTF32 — availability of UTF-32 support (1=yes 0=no); option for pcre32_config() ⭐
• PCRE_CONFIG_UTF8 — availability of UTF-8 support (1=yes 0=no); option for pcre_config() ⭐
• PCRE_CONFIG_UNICODE_PROPERTIES — availability of Unicode property support (1=yes 0=no) 🌈

The function yields 0 on success or PCRE_ERROR_BADOPTION otherwise 😤 That error is also given if:

• PCRE_CONFIG_UTF16 or PCRE_CONFIG_UTF32 is passed to pcre_config()
• PCRE_CONFIG_UTF8 or PCRE_CONFIG_UTF32 is passed to pcre16_config()
• PCRE_CONFIG_UTF8 or PCRE_CONFIG_UTF16 is passed to pcre32_config()

like, keep your functions and your options matched, bestie. it's giving compatibility. periodt 💅

There is a complete description of the PCRE native API in the pcreapi page 📖 and a description of the POSIX API in the pcreposix page 📖 — go read those if you want the full tea.

mwah 💜 that's the whole page. this one's from PCRE 8.36, dated 20 April 2014 — vintage but still slaying, fr fr. go forth and pcre_config() responsibly, queen 👑✨