EmbeddingGemma 2: an open, lightweight multimodal embedding model
deepmind.google·6d ago
AI Engineering
Lobsters·Aug 10·5 min read
an ambiguity in c89 which will never be fixed
TL;DR
An ambiguity in the C89 standard regarding implicit function declarations leads to differing interpretations between GCC and Clang. This issue, stemming from the standard's allowance for undeclared functions, remains unresolved since it was eliminated in C99.
✦ Why It Matters
Review your C89 code for implicit function declarations to avoid potential cross-compiler issues.
Key Takeaways
- Understand the implications of implicit function declarations in C89.
- Be aware of compiler differences when using legacy C standards.
- Consider updating codebases to C11 for better clarity and support.
- Avoid using C89 unless absolutely necessary for niche applications.
How It Works
C89 allows functions to be implicitly declared if they are called without prior declaration. This means that if a function is referenced before it is defined, the compiler assumes it returns an int and has unspecified parameters.
This can lead to unexpected behavior, especially when the function's name is used within its own declaration.
⚠ The Catch
The ambiguity in the C89 standard regarding 'innermost block' scope leads to different interpretations by GCC and Clang, causing inconsistencies in how function declarations are handled.