Excel-represented dates vs. Human-readable dates in UDFs

Hello

When you punch in a native function like

=TODAY()

you get a human-readable output, like 2/23/15. Yet a barebones UDF will spit out the excel representation of a date like 42058.

Here's a brief UDF for the sake of example. What am I missing of get a human-readable date as output that will still behave like an Excel date?

Function ForTheSakeOfExample(ByVal num As Integer) As Date
    
    If (num > 0) Then
        ForTheSakeOfExample = DateSerial(2015, 1, 1)
    Else
        ForTheSakeOfExample = Date
    End If
    
End Function

Originally Posted by MrShorty

Recognize that the "human readable" output is merely an appropriate number format code applied to a cell containing an appropriate serial number.

I suppose the heart of my question is why can a native formula like =TODAY() seem to know to change the number format code from "general" to "date" automatically, but my UDF requires me to change the number format code from "general" to "date" manually. My concern is for the general user of my UDF who will likely not realize that the serial number represents a date.

Not the answer I was hoping to hear, but thank you for the information. I'm marking this one SOLVED.