They are simply showed like this: _______________________ | <<enumeration>> | | DaysOfTheWeek | |_____________________| | Sunday | | Monday | | Tuesday | | … | |_____________________| And then just have an association between that and your class.
You absolutely can use is in a switch block. See “Type Casting for Any and AnyObject” in the Swift Programming Language (though it’s not limited to Any of course). They have an extensive example: for thing in things { switch thing { case 0 as Int: println(“zero as an Int”) case 0 as Double: println(“zero … Read more
“Plain Old C# Object” Just a normal class, no attributes describing infrastructure concerns or other responsibilities that your domain objects shouldn’t have. EDIT – as other answers have stated, it is technically “Plain Old CLR Object” but I, like David Arno comments, prefer “Plain Old Class Object” to avoid ties to specific languages or technologies. … Read more
Updated answer for Roxygen2 5.0.1, current as of 6.0.1 For S4, the best practice now is documenting using the @slot tag: #’ The title for my S4 class that extends \code{“character”} class. #’ #’ Some details about this class and my plans for it in the body. #’ #’ @slot myslot1 A logical keeping track … Read more
To be clearer, I make an example here, class ClassA { class func func1() -> String { return “func1” } static func func2() -> String { return “func2” } /* same as above final class func func2() -> String { return “func2” } */ } static func is same as final class func Because it … Read more