Scheme. Clojure. Lisp for High-Performance Transaction Processing. Azul Systems - Cliff Click Jr.’s Blog. Function inlining in JVMs is a solved problem, right? It's a key performance optimization routinely done by JIT's everywhere (some might say: THE key optimization). Inlining has more than a decade of fine tuning in the Java context and over 40 years of production experience in the compilers and systems before that. I'm off to another conference - this time TSSJS in Las Vegas. Well, I? M baaaaack?.. After a nearly year-long hiatus. About Unsafe and CompareAndSwap (and NonBlockingHashMap). A reader asked me: where is the volatile-like orderings guaranteed in NBHM?
CAS - Compare-And-Swap instruction (or on IBM Power chips: Load-Linked / Store-Conditional). Unsafe - Java-level access to raw memory. Gadzooks, time flies! Part 2: Lisbon to San Francisco, via Toronto - plus ISMM and PLDI 2010 ISMM & PLDI in Toronto, CA Skip to the techy parts... As mentioned in my last blog, I am flying into Toronto from Lisbon, Portugal. Please can I get a few comments from readers so I know the blog is functional? ``Condition Handling in the Lisp Language Family'' c b. This paper appears inAdvances in Exception Handling Techniques, edited by A. Romanovsky, C. Dony, J.L. Knudsen, and A. Tripathi. This book, published in 2001, is part of Lecture Notes in Computer Science, Volume 2022, published by Springer.
This paper was originally written as an HTML document, exactly as shown below. Any final reformatting that was done for hardcopy publication in LaTeX may have been lost in this version. Annotated original document follows.Click here for an index of other titles by Kent Pitman. Introduction The Lisp family of languages has long been a rich source of ideas and inspiration in the area of error handling. Although there are numerous dialects of Lisp, several of which offer the modern concepts and capabilities described herein, we will focus specifically on Common Lisp as described in the ANSI standard, X3.226-1994 [X3J13 1994].
Condition Systems vs Error Systems Not all exceptional situations are represented, or sometimes even detected. Historical Influences. Python-mode vs. slime - A view from the hill. Thoughts Reading Practical Common Lisp. In my last post I mentioned reading Practical Common Lisp. I went on through several more chapters since I wrote that (quite a few more) and one practically made me stop. The first “practical” exercise is writing a library that makes it less horrifically painful to use Common Lisp to deal with reading directories. It was a pretty quick little library and I’m sure effective, but at that time, I was kind of tired of hearing explanations of how “this has a meaningless name, for historical reasons,” or “this is completely contrary to how you’d expect it to be considering other parts of the language” or whatever.
There’s a lot to just get used to in Common Lisp. Seeing an entire “practical” chapter devoted to creating a library to fix kludgy implementation problems stemming from Common Lisp’s advanced age was offputting. But then I realized that a little ahead were the chapters on CLOS, the Common Lisp Object System, something I had always wanted to understand and never quite got.