Book Image

Hands-On Design Patterns and Best Practices with Julia

By : Tom Kwong
Book Image

Hands-On Design Patterns and Best Practices with Julia

By: Tom Kwong

Overview of this book

Design patterns are fundamental techniques for developing reusable and maintainable code. They provide a set of proven solutions that allow developers to solve problems in software development quickly. This book will demonstrate how to leverage design patterns with real-world applications. Starting with an overview of design patterns and best practices in application design, you'll learn about some of the most fundamental Julia features such as modules, data types, functions/interfaces, and metaprogramming. You'll then get to grips with the modern Julia design patterns for building large-scale applications with a focus on performance, reusability, robustness, and maintainability. The book also covers anti-patterns and how to avoid common mistakes and pitfalls in development. You'll see how traditional object-oriented patterns can be implemented differently and more effectively in Julia. Finally, you'll explore various use cases and examples, such as how expert Julia developers use design patterns in their open source packages. By the end of this Julia programming book, you'll have learned methods to improve software design, extensibility, and reusability, and be able to use design patterns efficiently to overcome common challenges in software development.
Table of Contents (19 chapters)
1
Section 1: Getting Started with Design Patterns
3
Section 2: Julia Fundamentals
7
Section 3: Implementing Design Patterns
15
Section 4: Advanced Topics

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...