Java Closures and Lambda
This book is the culmination of many brash years and hard lessons. The story starts all the way back when I migrated from C++ into perl. The perl programming language was amazingly powerful compared to the low-level manipulations and bookkeeping of C++. (The fact that it was “slow” never bothered...
Đã lưu trong:
| Tác giả chính: | |
|---|---|
| Định dạng: | Sách |
| Ngôn ngữ: | English |
| Được phát hành: |
Apress
2015
|
| Những chủ đề: | |
| Truy cập trực tuyến: | https://scholar.dlu.edu.vn/thuvienso/handle/DLU123456789/57282 |
| Các nhãn: |
Thêm thẻ
Không có thẻ, Là người đầu tiên thẻ bản ghi này!
|
| Thư viện lưu trữ: | Thư viện Trường Đại học Đà Lạt |
|---|
| Tóm tắt: | This book is the culmination of many brash years and hard lessons. The story starts all the way back when
I migrated from C++ into perl. The perl programming language was amazingly powerful compared to the
low-level manipulations and bookkeeping of C++. (The fact that it was “slow” never bothered me – I would
rather write powerful, effective slow code than weak, buggy fast code.) In the world of perl, there was the idea of
an “anonymous subroutine” that could be passed around and manipulated. You could also directly manipulate
the symbol table. The symbol table is the collection of function names available to the program. Between these
two things, I realized that I could code at a higher level: I could write subroutines that returned subroutines and
store those into the symbol table, effectively having my code write code at runtime. In perl, these subroutine
factories are called “template functions.” I proceeded to write some truly unreadable – but truly powerful – perl.
I shared this revelation with my friend and mentor, Brian Hurt. He was the grizzled veteran developer who
seemed to have seen it all. Brian told me that what I was doing was this thing called “functional programming,”
and encouraged me to look into proper functional languages, specifically OCaml, and its derivative, JoCaml... |
|---|