It is a gravely serious matter when a Lady begins trumpeting her hysterical Programming Notions about. It only ever ends in tears, and it makes the negroes restless.

Your floppy bosoms are blocking your reason-holes. www.lisp.org/table/style.htm Where are your mysterious ideas of "good practice" coming from?

This comment stream is as much fun as downing a pint of cold sick in a oner. You bulbous gonads.

Of course there can be no dialog. We both knew that from the start. Even though the general structure I’ve shown here is accepted as good practice there can be no admission of this. And of course I knew before starting that you’d resort to terms like “ladies world” and “cognitive level above that of a pea” to impress an air of authority. I will not convince you otherwise, so I won’t try.

I will hurt you later. Just watch because tommarow at school I am going to get you.

1. My dear, if 'food' was a function, it would have brackets around it to evaluate it. We both know it's not a reserved word. Let's face it, it's a global variable. 2. Anyone operating on a cognitive level above that of a pea is perfectly capable of matching up opening and closing parentheses without the aid of indentation. And since it's against convention, which makes it uncomfortable and annoying to read for people accustomed to convention, it's equivalent to wearing a bin on one's head and charging head-first into the sea. 3. I can't expect anyone without a billowing, rockmage-like beard to understand how comments actually tend to make code harder to read. Naive, comforting faith in comments is endemic to the ladies' world of AUTOCAD, and I doubt I will convince you otherwise, so I shan't bother.

‘food’ could be a reserved word in this version of LISP, a defined function in a higher file such as acad.lsp, a function called by an internal call that yields nil or not-nil, a command in the application, or it could be a global variable. The code is easier to maintain because it’s easier to follow. It’s easy to change a variable name and all of the comments that address it using a simple text search and replace. That’s how it’s done in the real world of nil beards.

P.S. Lisp code is itself a series of linked lists. Therefore your code does in fact "manage linked lists." PARP.

You're a thicky. 1. 'food' is either a global variable or an error. Stop disputing it, and stop randomly discharging Lisp syntax. 2. I'm well aware how expressions are formed. I am commenting on your formatting. Your formatting is unconventional and unhelpful. It may be considered "good practice" to put closing brackets on a separate line in the ladies' world of AUTOCAD. It is not considered good practice anywhere else. Lisp is not C. Go read some actual, non-AUTOCAD Lisp. You will see how it is done in the real world of enormous beards. 3. I don't fathom how you think it "makes the code easier to maintain". However, what doesn't make the code easier to maintain is your cutesy comments. They make it harder, because if you change the name of the function or variable, you have to go update the comment. It also insults the reader, clutters up the page, and makes you look like the only code you've ever seen was from an AUTOCAD tutorial, which is most likely the case. 4. It is "Lisp". Do not discharge what it stands for. 5. That you think "linked list" and "coordinate searches" are sophisticated, confusing computer phrases is both quaint and crushingly dim.

Thank you for a remarkable commentary on my poem, my ability as a LISP programmer, and on LISP itself. Particularly interesting is your pointing out that all of my variables are global since they are not defined locally. I suppose you are right since no variables are used in the hunger function - not locally as they would be with (defun hunger eat sleep crap . . .) or somesuch, nor are any global variables assumed by not being so defined. So that tells me about how much you know about LISP. Also, it is very common for a programmer to comment on a close paren, especially if several lines separate it from its open paren. As you may not know, every open paren in LISP must be followed eventually by a close paren which completes the command. Placing the close paren on a new line with a comment telling which open paren it closes is therefore good practice and makes the code easier to maintain. I tried to keep the program simple, avoiding parameter passing and uncommon commands that manage linked lists, coordinate searches and the like, but I see it is not simple enough. Of course nobody can dispute your expertise in swellington poemes and your ability to determine failure in all things poetic and LISP.