Search icon CANCEL
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Conferences
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
Hands-On Design Patterns and Best Practices with Julia

You're reading from   Hands-On Design Patterns and Best Practices with Julia Proven solutions to common problems in software design for Julia 1.x

Arrow left icon
Product type Paperback
Published in Jan 2020
Publisher Packt
ISBN-13 9781838648817
Length 532 pages
Edition 1st Edition
Languages
Arrow right icon
Author (1):
Arrow left icon
Tom Kwong Tom Kwong
Author Profile Icon Tom Kwong
Tom Kwong
Arrow right icon
View More author details
Toc

Table of Contents (19) Chapters Close

Preface 1. Section 1: Getting Started with Design Patterns
2. Design Patterns and Related Principles FREE CHAPTER 3. Section 2: Julia Fundamentals
4. Modules, Packages, and Data Type Concepts 5. Designing Functions and Interfaces 6. Macros and Metaprogramming Techniques 7. Section 3: Implementing Design Patterns
8. Reusability Patterns 9. Performance Patterns 10. Maintainability Patterns 11. Robustness Patterns 12. Miscellaneous Patterns 13. Anti-Patterns 14. Traditional Object-Oriented Patterns 15. Section 4: Advanced Topics
16. Inheritance and Variance 17. Assessments 18. Other Books You May Enjoy

Chapter 2

How do we create a new namespace?

A namespace is created using a module block. Typically, a module is defined as part of a Julia package.

How do we expose the functions of a module to the outside world?

Functions and other objects defined within a module can be exposed using an export statement.

How do we reference the proper function when the same function name is exported from different packages?

We can just prefix the function name with the package name. As an alternative, we can use a using statement for one package, and an import statement for the other, so that we can use the function name directly for the first package but use the prefix syntax for the other.

When do we separate code into multiple modules?

It is time to consider separating code into modules when the code becomes too big and too difficult to manage. We expect some refactoring to ensure the...

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 AU $24.99/month. Cancel anytime