Subject: Re: representing a network in lisp
From: Erik Naggum <>
Date: Tue, 09 Apr 2002 19:21:48 GMT
Newsgroups: comp.lang.lisp
Message-ID: <>

* Jochen Schmidt <>
| For *print-circle* particular nothing more but a speed penalty for 
| circularity checking.

  A speed penalty for the return value of evaluated forms in an interface
  based on sockets and printing values?  You cannot be for real.  This is
  just too damn silly to be an honest opinion.  Who is paying you for this?

| I said "variables like *print-circle*" which was meant to include other
| variables like *print-base* *print-readably*.

  And if you _want_ a different print base?  Are you just trolling?

| If you want to make sure that the code in the buffer uses the changed
| value then you should do this change in the code you want to evaluate.

  What is wrong with you?  Why do you not understand the value seen by the
  printer of the return value of a form _cannot_ be changed by the form
  itself?  My god, you cannot have thought about this issue at _all_!

  Do you know how a read-eval-print loop works at all?

| If you do not like the ACL behaviour then be free to use another
| lisp-system like Xanalys LispWorks which does not behave this way.

  Ah, there we have it.  You are an idiot marketing droid from Xanalys!
  "Do not change a trivial little thing, change your whole environment!"
  What kind of mindlessness is required to even _suggest_ this?

| This is true.  And I would find it confusing if you could not set the
| printer/reader-variables in a listener so that _this_ listener uses them
| for direct interaction.

  Hello?  Anybody home?  This is exactly what the discussion is about!

| This is actually a different issue.  I was not talking about setting this
| variables in your listener but about trying to set them in a buffer to
| evaluate and then thinking that it should have global effect.

  You have _no_ idea what this is about, do you?

| Having *print-circle* to T by default will mean always checking for 
| circularity which may not be needed or wanted too.

  What?  The other option is to limit the length or the level of the output
  so you cannot look at what really happened.  Well, the third option is to
  die horribly if you have circular structures, and that is a serious bug.

| I would have said the same if the default would have been T and someone
| wants to set it globally to NIL the way the OP did it. I think it should
| definitely be possible to change the global defaults (and actually it is
| of course possible).

  Actually it is, eh?  Dude, you are _really_ clueless.  Quit yapping if
  you do not even have the humility to ask before you spout idiotic drivel!

| This has nothing to do with the issue of having local bindings of this
| variables when a buffer evaluates.

  Yes, it does.  Clueless moron.  Stop spreading disinformation in the
  guise of marketing for Xanalys, will you?

  How _fantastically_ annoying it is to counter the nonsense and drivel
  from people who are so clueless that they do not even recognize when they
  are out of clues even before they start talking.  Man!

  Sheesh, some people.

  In a fight against something, the fight has value, victory has none.
  In a fight for something, the fight is a loss, victory merely relief.

  Post with compassion: