Question

Is it reasonable to have method in sealed class with greater accessability than the class itself.
Of course just not taking into consideration later refactoring…

Example

class SomeClass
{
    public void SomeMethod()
    {
        ...
    }
}

Answer 1

(My answer is for C# only)

Of course it can be useful!

Reason 1:

The access modifiers cannot all be put in order.

Would you say that protected was more accessable than internal, or less?

Reason 2:

Overriding bace class methods and implementing interfaces:

internal sealed class MyClass
{
    public override string ToString()
    {
        return "How would you do this without public methods?";
    }
}

Now by casting a MyClass to Object, the method can be exposed outside the assembily.

This pattern is often used when implementing IEnumerator. Often the real class will be private (not even internal).

Reason 3:

Access to a private nested class:

public class A
{
    public string TellMeWhy()
    {
        return B.TheReason;
    }

    sealed private class B
    {
        internal static string TheReason = 
            "How would you access any of these members " +
            "if they all have to be private?";
    }
}