PracticalCommonlisp资源-CSDN文库

5星 · 超过95%的资源需积分: 9 141 浏览量 2009-03-15 10:54:18 上传评论 10 收藏 2.65MB PDF 举报

资源推荐

资源详情

资源评论

Practical

Practical Common

Common

Common Lisp

Lisp

that book is dead sexy — Xach on #lisp

( more blurbs )

This page, and the pages it links to, contain text of the Common Lisp book

Practical Common

Lisp

published by Apress These pages now contain the final text

it appears in the book. If you

find errors in these pages, please send email to book@gigamonkeys.com . These pages will remain

online in perpetuity — I hope they will serve

a useful introduction to Common Lisp for folks

who are curious about Lisp but maybe not yet curious enough to shell out big bucks for a dead-tree

book and a good Common Lisp tutorial for folks who want to get down to real coding right away.

However, don't let that stop you from buying the printed version available from Apress at your

favorite local or online bookseller. For the complete bookstore browsing experience, you can read

the letter to the reader that appears on the back cover of the treeware edition of the book.

Going to be huge in Japan !

Japanese publisher Ohmsha is publishing a Japanese translation of Practical Common Lisp which

should be avaliable in bookstores July 26, 2008.

English version on its third printing

Amaz on | Powells | Barnes & Noble

Download

Download source

source

source code:

code:

code: tar.gz | zip

Now

Now available:

available:

available: Lispbox v0.7 distributions

Spread the word

Like what you've read? Then help spread the word. Recommend this book to your friends. Write a

review on Amaz on. Blog about it. Link to this page from your web site. Whatever. Apress took a

chance, publishing this book when other publishers thought there was no market for a Lisp book.

to learn some Lisp and see for yourself--thus the rest of this book. For now, let me start with some

anecdotal evidence, the story of my own road to Lisp. Then, in the next section,

I'll

explain the

payoff I think you'll get from learning Common Lisp.

I'm one of what must be a fairly small number of second-generation Lisp hackers. My father got

his start in computers writing an operating system in assembly for the machine he used to gather

data for his doctoral dissertation in physics. After running co mputer systems at various physics labs ,

by the 1980s he had left physics altogether and was working at a large pharmaceutical company.

That company had a project under way to develop software to model production processes in its

chemical plants--if you in crease the siz e of this vessel, how does it affect annual production? The

original team, writing in FORTRAN, had burned through half the money and almost

all

the time

allotted to the project with nothing to show for their efforts. This being the 1980s and the middle of

the artificial intelligence (AI) boom, Lisp was in the

air.

So my dad--at that point not a Lisper--

went to Carnegie Mellon University (CMU) to talk to some of the folks working on what was to

become Common Lisp about whether Lisp might be a good language for this project.

The CMU folks showed him some demos of stuff they were working on, and he was convinced. He

in turn convinced his bosses to let his team take over the failing project and do it in Lisp.

year

later, and using only what was left of the original budget, hi

team delivered a working application

with features that the original team had given

any hope of delivering. My dad credits his team's

success to their decision to use Lisp.

Now, that's just one anecdote. And maybe my

dad

is wrong about why they succeeded. Or maybe

Lisp was better only in comparison to other languages of the

day.

These days we have lots of fancy

new languages, many of which have incorporated features from Lis p. Am I really saying Lisp can

offer you the same benefits today

it offered my

dad

in the 1980s? Read on.

Despite my father's best efforts, I didn't learn any Lisp in high school. After a college career that

didn't involve much programming in any language, I was seduced by the

Web

and

back into

computers. I worked first in Perl, learning enough to be dangerou

while building an online

discussion forum for

Mother Jones

magazine's

Web

site

and

then moving to a

Web

shop, Organic

Online, where I worked on big--for the time--Web sites such

the one Nike put

during the

1996 Olympics. Later I moved onto Java

an early developer at WebLogic, now part of BEA.

After

WebL

ogic, I joined another startup where I was the

lead

programmer on a team building a

transactional messaging system in Java. Along the

way,

my general interest in programming

languages

led

me to explore such mainstream languages

C++,

and

Python,

ell

less

well-known ones such

Smalltalk, Eiffel,

and

Beta.

So I knew two languages inside

and

out

and

was familiar with another half doz en. Eventually,

however, I realiz ed my interest in programming languages was really rooted in the idea planted by

my father's tales of Lisp--that different languages really are d ifferent,

and

that, despite the formal

Turing equivalence of

all

programming languages, you really can get more done more quickly in

some languages than others

and

have more fun doing it.

Yet,

ironically, I

had

never spent that much

time with Lisp itself. So, I started doing some Lisp hacking in my free time. And whenever I did, it

was exhilarating how quickly I was able to go from idea to working code.

For example, one vacation, having a week

so to hack Lisp, I decided to try writing a version of a

program--a system for breeding genetic algorithms to play the game of Go--that I

had

written early

in my career

a Java programmer. Even handicapped by my then rudimentary knowledge of

Common Lisp

and

having to look

even basic functions, it still felt more productive than it would

have been to rewrite the same program in Java, even with several extra years of Java experience

acquired since writing the first version.

similar experiment

led

to the library

I'll

discuss in Chapter 24. Early in my time at WebLogic I

had

written a library, in Java, for taking apart Java class files.

worked, but the code was a bit of a

mess

and

hard to modify

extend. I

had

tried sev eral times, over the years, to rewrite that library,

thinking that with my ever-improving Java chops

I'd

find some way to do it that didn't bog down in

piles of duplicated code. I never found a

way.

But when I tried to do it in Common Lisp, it took me

onl y two days,

and

I ended

not only with a Java class file parser but with a general-purpose

library for taking apart any kind of binary file. You'll see how that library works in Chapter 24

and

use it in Chapter 25 to write a parser for the ID3 tags embe dded in MP3 files.

Why

Why Lisp?

Lisp?

It's hard, in only a few pages of an introductory chapter, to explain why users of a language like it,

and

it's even harder to make the case for why you should invest your time in learning a certain

language. Personal history only gets us so

far.

Perhaps I like Lisp because of some quirk in the way

my brain is wired.

could even be genetic, since my

dad

has it too. So before you dive into

learning Lisp, it's reasonable to want to know what the payoff is going to be.

For some languages, the payoff is relatively obvious. For instance, if you want to write low-level

code on Unix, you should learn

Or if you want to write certain kinds of cross-platform

applications, you should learn Java. And any of a number companies still use a lot of C++, so if

you want to get a job at one of them, you should learn C++.

For most languages, however, the payoff isn't so easily categoriz ed; it has to do with subjective

criteria such

how it feels to use the language. Perl advocates like to say that Perl "makes easy

things easy

and

hard things possible"

and

revel in the fa ct that,

the Perl motto has it, "There's

more than one way to do it."

Python's fans, on the other hand, think Python is clean

and

simple

and

think Python code is easier to understand because,

their

motto says, "There's only one way to do

it."

So, why Common Lisp? There's no immediately obvious payoff for adopting Common Lisp the

way there is for

Java,

and

C++ (unless, of course, you happen to own a Lisp Machine). The

benefits of using Lisp have much more to do with the experience of using i

I'll

spend the rest of

this book showing you the specific features of Common Lisp

and

how to use them so you can see

for yourself what it's like. For now

I'll

try to give you a sense of Lisp's philosophy.

The nearest thing Common Lisp has to a motto is the koan-like description, "the programmable

programming language." While cryptic, that description gets at the root of the biggest advantage

Common Lisp still has over other languages. More than any other language, Common Lisp follows

the philosophy that what's good for the language's designer is good for the language's users. Thus,

when you're programming in Common Lisp, you almost never find yourself wishing the language

supported some feature that would make your program easier to write, because,

you'll see

throughout this book, you can just

add

the feature yourself.

Consequently, a Common Lisp program tends to provide a much clearer mapping between your

ideas about how the program works

and

the code you actually write.

Your

ideas aren't obscured by

boilerplate code

and

endlessly repeated idioms. This makes your code easier to maintain because

you don't have to wade through reams of code every time you need to make a change. Even

systemic changes to a program's behavior can often be achieved with relatively small changes to

the actual code. This also means you'll deve lop code more quickly; there's less code to write,

and

you don't waste time thrashing around trying to find a clean way to express yourself within the

limitations of the language.

Common Lisp is also an excellent language for exploratory programming--if you don't know

exactly how your program is going to work when you first sit down to write it, Common Lisp

provides several features to help you develop your code incrementally

and

i nteractively.

For starters, the interactive read-eval-print loop, which

I'll

introduce in the next chapter, lets you

continually interact with your program

you develop it. Write a new function. Test it. Change it.

Try

a different approach.

You

never have to stop for a lengthy compilation cycle.

Other features that support a flowing, interactive programming style are Lisp's dynamic typing

and

the Common Lisp condition system. Because of the former, you spend less time convincing the

compiler you should be allowed to run your code

and

more time ac tually running it

and

working on

it,

and

the latter lets you develop even your error handling code interactively.

Another consequence of being "a programmable programming language" is that Common Lisp, in

addition to incorporating small changes that make particular programs easier to write, can easily

adopt big new ideas about how programming languages should work. F

instance, the original

implementation of the Common Lisp Object System (CLOS), Common Lisp's powerful object

system, was

a library written in portable Common Lisp. This allowed Lisp programmers to gain

actual experience with the facilities it provid

before it was officially incorporated into the

language.

Whatever new paradigm comes down the pike next, it's extremely likely that Common Lisp will be

able to absorb it without requiring any changes to the core language. For example, a Lisper has

recently written a library, AspectL, that adds support for aspec t-oriented programming (AOP) to

Common Lisp.

If AOP turns out to be the next big thing, Common Lisp will be able to support it

without any changes to the base language

and

without extra preprocessors

and

extra compilers.

Where

Where It

It Began

Began

剩余580页未读，继续阅读

评论收藏

内容反馈

zsxywz0928

2013-12-23

最近刚看完黑客与画家，准备开始用这本书学习common lisp~~~
yularna

2015-07-01

经典电子书，珍藏了
wwsAmigo

2013-01-10

好书啊，很厚的书。。希望有时间仔细学学！
wangyaosuper

2012-06-10

不错，这一本是学习lisp的经典。
thunderlam

2011-11-08

很好的lisp入门，现在好像Lambda 开始流行起来了

前往

页

eagle_m

粉丝: 4
资源: 4

Practical Common lisp

最新资源

Practical Common lisp

practical common lisp

Practical Common Lisp

实用Common.Lisp编程

practical common lisp英文版mobi

Practical Common LISP(Apress,2012)

Practical Common Lisp笔记

Common LISP书籍中文版pdf格式带书签.rar

Practical Common Lisp-1st-2005

Practical_Common_Lisp

Practical Common Lisp pdf

Practical Common Lisp(epub)

practical common lisp.pdf

Practical Common Lisp 英文版

Common lisp入门教程

lisp-notes:Common Lisp 的示例代码库

lisp-turing-machine：Common Lisp中的图灵机实现

eclipse-lisp:Eclipse Common Lisp

unificacion-lisp:Common LISP中的统一算法实现

common lisp的升级学习

Successful Lisp How to Understand and Use Common Lisp - David B. Lamkins

Common_lisp_The_Language_2nd_Edition

common-lisp-snippets：Common Lisp的Yasnippets

最新资源