Search icon CANCEL
Subscription
0
Cart icon
Your Cart (0 item)
Close icon
You have no products in your basket yet
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
Learn Kotlin Programming

You're reading from   Learn Kotlin Programming A comprehensive guide to OOP, functions, concurrency, and coroutines in Kotlin 1.3

Arrow left icon
Product type Paperback
Published in May 2019
Publisher Packt
ISBN-13 9781789802351
Length 514 pages
Edition 2nd Edition
Languages
Arrow right icon
Authors (2):
Arrow left icon
Stefan Bocutiu Stefan Bocutiu
Author Profile Icon Stefan Bocutiu
Stefan Bocutiu
Stephen Samuel Stephen Samuel
Author Profile Icon Stephen Samuel
Stephen Samuel
Arrow right icon
View More author details
Toc

Table of Contents (21) Chapters Close

Preface 1. Section 1: Fundamental Concepts in Kotlin FREE CHAPTER
2. Getting Started with Kotlin 3. Kotlin Basics 4. Object-Oriented Programming in Kotlin 5. Section 2: Practical Concepts in Kotlin
6. Functions in Kotlin 7. Higher-Order Functions and Functional Programming 8. Properties 9. Null Safety, Reflection, and Annotations 10. Generics 11. Data Classes 12. Collections 13. Testing in Kotlin 14. Microservices with Kotlin 15. Section 3: Advanced Concepts in Kotlin
16. Concurrency 17. Coroutines 18. Application of Coroutines 19. Kotlin Serialization 20. Other Books You May Enjoy

Packages

Packages allow us to split classes and interfaces into separate namespaces. A package may contain any number of classes and interfaces. Any file may begin with a package declaration:

    package com.packt.myproject 
    class Foo 
    fun bar(): String = "bar" 

The package name is used to give us the fully qualified name (FQN) for a class, object, interface, or function. In the preceding example, the Foo class has the fully qualified name of com.packt.myproject.Foo, and the top-level bar function has the fully qualified name of com.packt.myproject.bar.

Kotlin differs from Java in that the directory structure does not have to match the package name. For example, in Java, a com.packt.Foo class must reside in a file such as ./com/packt/Foo.java. Kotlin does not have this restriction.
lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at $19.99/month. Cancel anytime
Banner background image