为何Minix中strcpy定义于Lint_strcpy.c？Lint前缀含义及设计意图？

Great question — this gets into some neat history of C tooling and how Minix structures its standard library. Let's break it down:

First: What Does the Lint_ Prefix Mean? #

Back in the early days of C, before modern static analyzers existed, there was a tool called Lint — the original static code checker. It scanned C code to catch bugs like buffer overflows, type mismatches, undefined behavior, and non-portable code that compilers might miss.

Minix's Lint_* files are Lint-specific adapter implementations/stubs. They're not meant to be used when compiling code for execution; instead, they exist solely to let the Lint tool properly analyze code that uses these functions:

• Sometimes, Minix's actual runtime implementation of standard functions like strcpy is written in assembly (for maximum performance) or tucked away in a complex, compiler-optimized file that Lint can't parse. The Lint_strcpy.c provides a simple, pure-C version that follows Lint's expected rules, so the tool can do its job of checking for misuse (like unsafe buffer handling).
• Other times, Lint has strict expectations for how standard functions should behave. The Lint_* version enforces those "standard" behaviors for analysis, even if the runtime version has Minix-specific optimizations.

Why strcpy Is in Lint_strcpy.c But strpcpy Is in strpcpy.c #

The key difference here is whether the function is a standard C library function or a Minix-specific extension:

• strcpy is a core C standard function. Lint has well-established rules for checking its usage, so Minix needs a separate Lint-friendly version to ensure the tool can properly flag issues. The actual runtime strcpy is probably elsewhere (like an assembly file) — the Lint_strcpy.c is just for analysis.
• strpcpy is a non-standard extension (it's a Minix-specific variant that returns a pointer to the end of the destination buffer). Since Lint doesn't have pre-built rules for non-standard functions, there's no need for a separate Lint adapter. The regular strpcpy.c file serves both as the runtime implementation and as the version Lint uses for analysis.

The Point of This Design #

This split balances two goals:

1. Performance for runtime: Minix can optimize standard functions like strcpy with assembly or highly tuned code without worrying about Lint's parsing limitations.
2. Effective static analysis: Developers can still use Lint to catch bugs in code that uses these standard functions, thanks to the Lint-friendly stubs in Lint_* files.

For non-standard functions like strpcpy, there's no tradeoff needed — a single C implementation works for both runtime and analysis, so they live in regular-named files.

内容的提问来源于stack exchange，提问作者yomol777