Java casts and narrowing — which of the following lines are legal (compile successfully)? 1) int w = (int)888.8; 2) byte x = (byte)1000L; 3) long y = (byte)100; 4) byte z = (byte)100L; Assume standard Java primitive conversion rules.

Introduction / Context:Java allows explicit narrowing primitive conversions even when information will be lost. This question asks which given assignments compile; the focus is legality (compilation), not value correctness at runtime.

Given Data / Assumptions:

• All lines use explicit casts where narrowing is required.
• Values may overflow the target type; compilation only requires a proper cast.

Concept / Approach:Narrowing conversions (e.g., double → int, long → byte) require an explicit cast. Widening conversions (e.g., byte → long) are automatic. When an explicit cast is provided, the compiler accepts the conversion, even if the resulting value wraps or truncates.

Step-by-Step Solution:

Verification / Alternative check:Remove the casts in lines 2 and 4 and compilation fails (possible lossy conversion). Keeping casts ensures success.

Why Other Options Are Wrong:

• Options selecting subsets ignore that all four lines compile under Java’s casting rules.

Common Pitfalls:Assuming the compiler rejects narrowing even with a cast; in fact it compiles but may change the runtime value.

Final Answer:All statements are correct.