Singleton class implementing an interface

Question

Possible Duplicate:
What is so bad about Singletons?

One of the drawbacks of using Singleton, as widely discussed in this stackoverflow question is that they hide the class dependencies in the code. However, we can make a singleton implement an interface while still obeying the two rules of singleton: single instance and global scope.
Why is Singleton still said to hide dependencies?

Answer 1

Hiding dependencies means there is no visible link from your code to the singleton, as the singleton can be called from anywhere. Having the singleton implementing an interface doesn't change the problem.