Reading PAIP

How should I be prepared before I read PAIP? All I can think of is SLIME. Any CL implementation recommendations?

SBCL

You should read STFU and GTFO first.

>>3
Ahaha funny ;-)

What's name of that Jewish CL implementation?

>>5
Clisp. It's also the preferred CL implementation of Paul Graham.

>>6
Yeah, because he's a Lisper who "gets things done", right? Five years, writing a language in Scheme that doesn't even do anything. Yeah, take his advice. What projects does he have to show as evidence that his opinion matters? Do you see any source code other than that poor excuse for five years, Arc? SBCL is the fastest CL, the most advanced in features and userbase. Also, last time I checked, it doesn't work on Windows, which makes it even better.

>>7
Actually, it does work on Windows. There is a crude port, but technically it works.
Also, I think that >>6 mentioned PG to discourage me from using Clisp.

>>7
Also, last time I checked, it doesn't work on Windows, which makes it even better.
Seriously? Not even under Cygwin or MinGW?

>>9
Only in the same way that Internet Explorer works on Linux under Wine HQ.

>>10
IE 6 works fine under Wine.

>>1
SBCL is fine. PAIP very rarely uses anything implementation-specific.

Yeah, unlike SICP^[1] :(

^[1]Processor time functions

^penispenis_penis

I'll be having some HASKELL questions. Well, one question.

Is   car = head   as fast as   car l = head l   ? Certain people claim that it is not, but I can't see why.

The SBCL's error messages make me sad after all these nice and tidy GHC messages :(

>>15
1. Use fprintf ("fast printf") instead of printf.
2. ++i is faster than both i++ and i = i + 1.
3. void main(void) is faster than int main(void) or int main(int, char **) since no value needs to be returned to the OS.
4. Swapping with exclusive-or (a^=b^=a^=b swaps a and b) is faster than using a temporary. This works for all types (including structures), but not on all compilers. Some compilers may also give you a harmless warning.
5. Static storage duration objects are faster than automatic storage duration objects because the CPU doesn't have to set aside storage on the stack every time a function is called. Make your loop indexes global so that you can use them everywhere:
int i;
void func(void) { for (i = 0; i < 10; i++) ; /* ... */ }
void func2(void) { for (i = 0; i < 20; i++) ; /* ... */ }
/* ... */
6. Compilers often give more memory to arrays than you asked for. Here's how to check how big an array actually is (memset returns a null pointer if the size you passed to it is bigger than the size of the array you passed to it):
int arr[256];
size_t realsize;
for (realsize = 0; realsize <= SIZE_MAX; ++realsize)
        if (!memset(arr, 0, realsize)) break;
/* now you know that arr actually has realsize / sizeof (int) elements */
If you combine this with #5, your program will be faster in the long run (but this usually doesn't work for short programs).

>>15

That's an identity. How can 'car = head' and 'car l = head l' not be the same thing?

>>18
car = head conforms to Pointless style, and is therefore superior in every way.

Point-free

>>18
equality of function is undecidedalblaeoucradoedhaeooohadtoaeanhtdaoinhtdoaebm;wqjkkkkkkkkkkkkkkkhdt;qjkhtdn;qjkdhtnjqkntdhkjqtdhkqj;hdtjdhktjkq;drgcoeudgcugcoicrrrrrrrrrroooooooeuihdoeuiiiiiiiiiiiiiidhoeuiiiiiiiiiiiiiidhoeuidhtoeiutdhneuiodhtueiodhtoeuidthoeutdhiuedhtoeuiihdtoeuidoeuiddgodgodgodgodgodgodgeodeiuaoeuuuuuuclrgggggggggggggggaoeucrlguaeogaeuocrlgaeuorgclaeuorgclaoeurctatrlpi.tcrtritr.irpitrptirtairpcauiedehbftgcnrridueoauidhtchgip.yfgcrl/=lrcgfcrcgcrcg

>>18
equality of function is undecidedalblaeoucradoedhaeooohadtoaeanhtdaoinhtdoaebm;wqjkkkkkkkkkkkkkkkhdt;qjkhtdn;qjkdhtnjqkntdhkjqtdhkqj;hdtjdhktjkq;drgcoeudgcugcoicrrrrrrrrrroooooooeuihdoeuiiiiiiiiiiiiiidhoeuiiiiiiiiiiiiiidhoeuidhtoeiutdhneuiodhtueiodhtoeuidthoeutdhiuedhtoeuiihdtoeuidoeuiddgodgodgodgodgodgodgeodeiuaoeuuuuuuclrgggggggggggggggaoeucrlguaeogaeuocrlgaeuorgclaeuorgclaoeurctatrlpi.tcrtritr.irpitrptirtairpcauiedehbftgcnrridueoauidhtchgip.yfgcrl/=lrcgfcrcgcrcg

All work and no play makes Jack a dull boy
 All work and no play makes Jack a dull boy
 All work and no play makes Jack a dull boy
 All work and no play makes Jack a dull boy
 All work and no play makes Jack a dull boy
 All work and no play makes Jack a dull boy
 All work and no play makes Jack a dull boy
 All work and no play makes Jack a dull boy
 All work and no play makes Jack a dull boy
All work and no play makes Jack a dull boy
 All work and no play makes Jack a dull boy
 All work and no play makes Jack a dull boy
 All work and no play makes Jack a dull boy
 All work and no play makes Jack a dull boy
 All work and no play makes Jack a dull boy
 All work and no play makes Jack a dull boy
 All work and no play makes Jack a dull boy
 All work and no play makes Jack a dull boy

bampu pantsu