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
The Clojure Workshop

You're reading from   The Clojure Workshop Use functional programming to build data-centric applications with Clojure and ClojureScript

Arrow left icon
Product type Paperback
Published in Jan 2020
Publisher Packt
ISBN-13 9781838825485
Length 800 pages
Edition 1st Edition
Languages
Arrow right icon
Authors (5):
Arrow left icon
Konrad Szydlo Konrad Szydlo
Author Profile Icon Konrad Szydlo
Konrad Szydlo
Yehonathan Sharvit Yehonathan Sharvit
Author Profile Icon Yehonathan Sharvit
Yehonathan Sharvit
Scott McCaughie Scott McCaughie
Author Profile Icon Scott McCaughie
Scott McCaughie
Thomas Haratyk Thomas Haratyk
Author Profile Icon Thomas Haratyk
Thomas Haratyk
Joseph Fahey Joseph Fahey
Author Profile Icon Joseph Fahey
Joseph Fahey
+1 more Show less
Arrow right icon
View More author details
Toc

Table of Contents (17) Chapters Close

Preface 1. Hello REPL! 2. Data Types and Immutability FREE CHAPTER 3. Functions in Depth 4. Mapping and Filtering 5. Many to One: Reducing 6. Recursion and Looping 7. Recursion II: Lazy Sequences 8. Namespaces, Libraries and Leiningen 9. Host Platform Interoperability with Java and JavaScript 10. Testing 11. Macros 12. Concurrency 13. Database Interaction and the Application Layer 14. HTTP with Ring 15. The Frontend: A ClojureScript UI Appendix

What is a Macro?

A macro is a piece of code that is executed before your code is compiled. The code contained inside a macro call is transformed into something different and then passed on to the compiler. In Clojure, macros are defined by calling defmacro. A call to defmacro looks fairly similar to a call to defn:

(defmacro my-macro
  "Macro for showing how to write macros"
  [param]
  ;;TODO: do something
  )

Despite this apparent similarity, there is a huge difference between macros and functions. Unlike functions, macros are not called at runtime. When your program finally starts running, the macros have already been called. The code they produce has already been included in your program as if you had typed it in yourself:

Figure 11.1: Separating compile time from runtime is the key to understanding macros

Keep this idea in mind while you think about and work with macros: any macro in your code could...

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 R$50/month. Cancel anytime