Hey, Jürgen,

I've publish a few novels through Amazon, and, yeah, they can be expensive.  But before I started with Amazon I used a company called LuLu (lulu.com) that does print-on-demand, both hardcover and paperback, as well as ebooks.  (Nothing wrong with Lulu, I just switched to Amazon because they had better marketing services for fiction.)

No idea if Lulu prices are any different than Amazon's, but they definitely ship to the US and I'm pretty sure world-wide.  (I used to work for a company called Red Hat, an intensely international place, and Lulu was founded by one of Red Hat's co-founders.)

Henrik

On 10/3/26 10:50, Dr. Jürgen Sauermann wrote:
Hi Henrik,

that's a real pity. In particular since I checked with the publisher (BoD) beforehand if the can/will be sold in the US. To make that possible I had to change from hard-cover (which I normally prefer) to paperback. I will complain at BoD about this, but have little hope that
they will change their distribution channel.

I also looked on the Web for other book stores offering the book. Most of them, like BoD
itself, ship only within the EU.

Finally I looked at Amazon.com in the US. It seems like they offer (and ship) the book in the US. Unfortunately the price is significantly higher - the book sells for €78,00 ∼ $88,00 in Europe, but for $107,50 at Amazon US). I suppose this is due to recent US tariffs for European goods.

Best Regards,
Jürgen


On 10/2/26 22:52, Henrik Moller wrote:
I guess I missed the announcement last week, but, first, at least if you're using the Brave browser and maybe have the right extensions installed, right-clicking on the bookstore pages gets you translations.  Second, the bookstore doesn't seem to ship to the US.

On 10/1/26 14:32, Robin Haberkorn via Bugs and suggestions for GNU APL wrote:
Congratulations, Jürgen!

I discovered your book even before you announced it. I was looking
for *something* about APL and there it was.

Books on Demand is quite expensive, though. Are you planning
a digital release as well?

Best regards,
Robin

On Sun Sep 27, 2026 at 21:10:17 GMT +02, Dr. Juergen Sauermann via Bugs and suggestions for GNU APL wrote:
Hi all,

I'm happy to announce that I've finished a book about GNU APL:

*The GNU APL Bible: Implementing APL in C++*

It's a 324-page, chapter-by-chapter walk through the actual
implementation: the core data model (Value, Shape, ravel, the Cell
hierarchy), the execution pipeline (tokenizer, parser, prefix, the
state indicator), built-in functions and operators, symbol and
workspace management, and the more advanced corners -- the libapl
embedding API, native functions and auxiliary processors, parallel
execution, the WebSocket/GUI interfaces, and the Windows port. A final
part is aimed squarely at anyone who wants to contribute: navigating
the source tree, common maintenance tasks, debugging techniques, and
the Savannah/mailing-list workflow itself. Style is deliberately
modeled on Knuth's "The Art of Computer Programming" -- annotated code
listings, historical notes, and exercises at the end of each chapter.

A free preview -- front cover, the full table of contents (with the
same page numbers as the printed book), the preface, and Chapters 1-3
in full -- is at *HOWTOs/Bible/Bible-Preview.pdf* in your *SVN 2128* or *Git* checkout (just *svn up*, or *git pull*), or directly from Savannah:

http://svn.savannah.gnu.org/viewvc/apl/trunk/HOWTOs/Bible/Bible-Preview.pdf

Detailed ordering instructions for the whole book are at the end of
the preview.

I hope this is a useful companion for anyone maintaining, extending,
or just curious about what's actually going on inside GNU APL.

Best regards,
Jürgen






  • Announcing &qu... Dr. Juergen Sauermann
    • Re: Annou... Robin Haberkorn
      • Re: A... Dr . Jürgen Sauermann via Bugs and suggestions for GNU APL
      • Re: A... Henrik Moller
        • R... Dr . Jürgen Sauermann via Bugs and suggestions for GNU APL
          • ... Henrik Moller
          • ... Dr . Jürgen Sauermann via Bugs and suggestions for GNU APL
            • ... Blake McBride

Reply via email to