Safety margin under NAME_MAX (the real limit is 255 bytes on a single filesystem path component, not the ~260-char Windows MAX_PATH this repo’s filesystem has long-path support active, so total path length is not the binding constraint).
Existing baseline filenames as long as 203 chars already write fine and must not be disturbed, so this is set well above ordinary names and only engages for truly pathological ones (e.g. an unexpanded macro invocation misparsed by Doxygen as a function name, confirmed up to 3001 chars in a real SDK header).
Instance Variables
int ude.interfaces.MAX_COMPONENT_CHARS
Generated with Flude
Copyright © 2026