Java - Packages and Access Control
Consider this code:
package com.example;
public class Demo {}
// In another file:
import com.example.*;
import com.example.Demo;
What is the problem here?
Consider this code: package com.example; public class Demo {} // In another file: import com.example.*; import com.example.Demo; What is the problem here?
medium📝 Debug Q7 of 15
Step-by-Step Solution
Solution:
Step 1: Analyze imports
Importing 'com.example.*' already includes Demo class, so importing Demo explicitly is redundant.Step 2: Understand Java import rules
Java compiler ignores redundant imports and allows them; no compilation error occurs.Final Answer:
No problem, code is correct -> Option AQuick Check:
Redundant imports are allowed in Java [OK]
Quick Trick: Redundant imports via wildcard and explicit are fine [OK]
Common Mistakes:
- Thinking duplicate imports cause compile errors
- Confusing with ambiguous name imports
- Assuming class visibility issues
Master "Packages and Access Control" in Java
Want More Practice?
15+ quiz questions · All difficulty levels · Free
Free Signup - Practice All QuestionsMore Java Quizzes