3 ms·
You will at least be able to recognize the symptoms of Greenspun's Tenth (http://lispers.org/ http://lispers.org/) in your C code and know when to cut your loss
by arto 17y ago
You will at least be able to recognize the symptoms of Greenspun's Tenth (http://lispers.org/ http://lispers.org/) in your C code and know when to cut your losses in those cases when C is not the best possible fit to the problem domain at hand.
- andrewcooke 17y agofor my money, this is the best argument here. c memory handling is so painful, and support for higher order functions so limiting, that there really is very little that you can carry across directly from lisp and/or functional programming to c. on the other hand what you do see, is how much time you are wasting due to c's constraints; something that may help you better allocate your time and/or choose your tools. there are other small wins too. sometimes knowing the "easy way" to solve a problem you can then work out a compromise in c that gives you some of the benefits without being too hard to implement. as a result you can end up using realloc much more than other people you work with :o)