Case in point: I just ran across this in the SQLite 3 Overview:
In most other SQL database engines the datatype is associated with the table column that holds the data - with the data container. In SQLite 3.0, the datatype is associated with the data itself, not with its container. Paul Graham in his book ANSI Common Lisp calls this property "Manifest Typing". Other writers have other definitions for the term "manifest typing", so beware of confusion. But by whatever name, that is the datatype model supported by SQLite 3.0.
There are dozens of other possible references for this behavior. It's the type model used in Perl, as well as many other dynamic languages. But somehow invoking the name Paul Graham makes the idea less scary to those who take issue with this unorthodox database behavior.
I'm taking bets on how long before there is a groundswell to invoke the name of Paul Graham as a justification for a full-fledged macro system, or continuation-based web frameworks.
Continuations and the web (Score:1)
Re:Continuations and the web (Score:2)
Continuations (Score:2)
Continuations are one of the things (among others, I'm told) that Ruby borrowed from Lisp. At least one framework, Borges [rubyforge.org], uses continuations as a way to deal with state.
Unfortunately, I'm not one of those people smart enough to figure out how I can use continations to my advantage in daily work.
Re:Continuations (Score:1)
Almost every web app spends most of its time just recreating a state that it understands. And the logic of transitions between pages have to be unrolled into a big switch statement up front.
If perl 7 had continuations, you could do this: