Foreword
When Dave asked last year if I wanted to cowrite a book about Mason, I mused over the idea for a few hours but ultimately declined. I’ve already written a good deal about Mason in documentation and articles and wouldn’t want the book to become a rehash of my particular point of view. On a more personal level, the thought of creating any text longer than a few pages fills me with trepidation. Given the choice of eight hours of backbreaking Perl coding or an hour of writing, I’d take the code any day.
This book was authored, instead, by two Mason developers who have a fresh perspective and who, apparently, like writing as well as coding. Dave and Ken have been involved with Mason for years; they’ve contributed to the project immeasurably, first in discussions and later to the Mason core itself. I cannot imagine two people better suited for this book.
When authors have unfettered access to the CVS repository, as Dave and Ken do, the writing process ends up shaping the product itself (e.g., “I just wrote about this feature but it turns out it doesn’t exist—I’m going to implement it” or “I just wrote about this feature and it’s horrible, can we kill it?”). As a result, Mason has grown over the past year in ways I never would have predicted.
Read Chapter 12, for example, to see the new parsing/compiling infrastructure so insanely flexible that one can compile Mason into Embperl or replace Mason’s syntax with an XML variant. (Consider the original parser, a single 371-line subroutine, ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access