TypeScript lets you do inheritance in Javascript, but the restrictions are enforced at compile time, rather than the typical Javascript tendency to randomly throw errors whenever the browser feels like it.<\/p>\n
Part of this is enforcement of access specification:<\/p>\n
\nclass Dialog {\n message: String;\n \n render() {\n }\n \n public e() {\n console.log(\"e\"); \n }\n \n protected f() {\n console.log(\"f\");\n }\n \n private g() {\n console.log(\"g\");\n }\n}\n\nclass AlertDialog extends Dialog {\n render() {\n this.e();\n this.f();\n } \n\n public e() {\n super.e();\n console.log(\"e - child\"); \n } \n protected f() {\n console.log(\"f - child\");\n }\n}\n\nlet ad: Dialog = new AlertDialog();\nad.render();\n<\/pre>\nThis prints out the following:<\/p>\n
\ne\ne - child\nf - child\n<\/pre>\nFrom this you can see that you can’t call private methods outside their own class, and protected methods are automatically virtual methods that override the parents. Public is available as an access specifier for completeness, but not necessary.<\/p>\n","protected":false},"excerpt":{"rendered":"
Demonstration of how to do access specification on TypeScript classes<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"om_disable_all_campaigns":false,"_monsterinsights_skip_tracking":false,"footnotes":""},"categories":[4],"tags":[302,557],"aioseo_notices":[],"aioseo_head":"\n\t\t\n\t\n\t\n\t\n\t\n\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t