- Hands-On Design Patterns with Kotlin
- Alexey Soshin
- 90字
- 2021-06-25 20:49:23
Naming conventions
As a convention, if your file contains a single class, name your file the same as your class.
If your file contains more than one class, then the filename should describe the common purpose of those classes. Use CamelCase when naming your files, as per the Kotlin Coding Conventions: https://kotlinlang.org/docs/reference/coding-conventions.html#naming-rules.
Actually, you don't have to write your code in a file for simple snippets. You can also play with the language online: try http://kotlinlang.org/ or use REPL and interactive shell after installing Kotlin and running kotlinc.
推薦閱讀
- Data Visualization with D3 4.x Cookbook(Second Edition)
- .NET之美:.NET關鍵技術深入解析
- Java Web開發學習手冊
- OpenDaylight Cookbook
- Testing with JUnit
- INSTANT OpenCV Starter
- LabVIEW2018中文版 虛擬儀器程序設計自學手冊
- PaaS程序設計
- Hadoop+Spark大數據分析實戰
- SEO智慧
- Effective Python Penetration Testing
- Node.js Design Patterns
- Getting Started with LLVM Core Libraries
- Visualforce Developer’s guide
- Learning Material Design