On Thu, Jan 8, 2009 at 12:42 PM, John Nilsson <[email protected]> wrote:
> While lisp may be a nice language to write, it is certainly not a good > language to read... I think this isn't so much the fault of the language as it is the fault of the way most Lisp code seems to be written. It is common to find code where a multi-step process is coded as a single function call, taking multiple arguments that are each function calls taking multiple argument, on and on. The code can often be made easier to read by simply applying the "extract method" refactoring pattern repeatedly. It's too bad more developers that work in Lisp-dialects don't take to the time to write their code so it is easy to read. Failure do so discourages other developers from learning and using the language. -- R. Mark Volkmann Object Computing, Inc. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "The Java Posse" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/javaposse?hl=en -~----------~----~----~----~------~----~------~--~---
