W8004
C++ Builder Programming Language
Severity: MinorWhat Does This Error Mean?
W8004 is a warning that a variable receives a value that the program never reads before the variable goes out of scope or is overwritten. This usually signals dead code — a calculation or assignment result that was meant to be used but is not. The fix is to either use the value where it was intended, remove the assignment, or remove the variable entirely.
Affected Models
- C++ Builder 10.x (Alexandria)
- C++ Builder 11 (Sydney)
- C++ Builder 12 (Athens)
- RAD Studio 11 and 12
Common Causes
- A variable is assigned inside a loop or function but the value is never read afterwards
- A return value from a function call is stored in a variable that is never used
- A calculation result is assigned to a local variable that is then overwritten before being read
- Code was refactored and a variable assignment became orphaned when the using code was removed
How to Fix It
-
Read the warning message — it names the exact variable and line. Trace forward from that assignment to see if the value is ever read before the variable is reassigned or destroyed.
W8004 is a genuine code-quality signal. An unused assignment usually means either a logic error (you forgot to use the result) or dead code (the assignment can be deleted).
-
If the value should have been used, find the missing use and add it. For example, a calculated result may need to be passed to a function or returned from the enclosing method.
This is the most important case — an unused assignment often reveals a logic error where a computed result silently disappears.
-
If the assignment is genuinely not needed, remove it. Delete the variable if it is no longer used at all, or simply remove the assignment statement.
Removing dead assignments keeps the code clean and helps the compiler optimize better. If you are keeping the variable for future use, a comment explaining why is better than leaving a ghost assignment.
Frequently Asked Questions
Can I suppress W8004 if the unused assignment is intentional?
Yes — add #pragma warn -8004 before the affected line and #pragma warn +8004 after to re-enable it. However, an intentional unused assignment is rare. Consider whether the code logic is actually correct before suppressing the warning.