PATHLEN falls back to 128 on default builds...

[onyxring]

The LINUX and MACOS settings for PATHLEN use 8192, PC_WIN32 uses 512, but the default build...

cc -O2 -o inform *.c

...drops to the fallback of 128.

I'm hitting it on a personal project: a deeply-nested tree plus several include search roots, where the accumulated +include_path overruns 128 characters. There are workarounds (shorter/relative paths; rebuild with a larger DPATHLEN setting) so it's not urgent, but 128 feels like an anachronistic default which people following the build instructions in the README will hit.

Could the default be bumped to match macOS/Linux (8192) by raising the fallback?

Looks like a one-line change.

[erkyrath]

It's an old default, but is that really going to discomfit people? The README says to use the appropriate define.

We could be more explicit about using -DMACOS or -DLINUX.

(Now that I look, -DUNIX should be brought in line with -DLINUX.)

[onyxring]

Yeah. It's just a suggestion on something that bit me, since I built the binary using the default example command line. The default version worked fine until I hit this particular issue and it took me a bit of digging through the code to understand what should have been obvious.

We could be more explicit about using -DMACOS or -DLINUX.

That would probably be sufficient if raising the default has some unintended consequences. Perhaps listing the top four or five symbols in the README would save someone the step of looking it up in the header.h file?